Client device for use with game token nfts and methods for use therewith

ABSTRACT

A client device operates by: providing a wallet associated with the user configured to store non-fungible tokens (NFTs); reading, via the camera, an optical code associated with a game token; sending, via the network interface and in response to reading the optical code, a request to download a game token NFT associated with the game token from an NFT distribution platform; receiving from the NFT distribution platform, via the network interface, the game token NFT associated with the game token; and storing the game token NFT in the wallet associated with the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. § 119(e) to U.S. Provisional Application No. 63/386,070,entitled “SYSTEMS FOR COUPON NFT TRANSACTIONS AND METHODS FOR USETHEREWITH”, filed Dec. 5, 2022; U.S. Provisional Application No.63/386,074, entitled “SYSTEMS FOR GENERATING COUPON NFTS AND METHODS FORUSE THEREWITH”, filed Dec. 5, 2022, U.S. Provisional Application No.63/386,078, entitled “SYSTEMS FOR AUTHENTICATING COUPON NFTS AND METHODSFOR USE THEREWITH”, filed Dec. 5, 2022; U.S. Provisional Application No.63/386,081, entitled “SYSTEMS FOR USE WITH LOYALTY PROGRAM NFTS ANDMETHODS FOR USE THEREWITH”, filed Dec. 5, 2022; and U.S. ProvisionalApplication No. 63/386,220, entitled “SYSTEMS USING GAME TOKEN NFTS ANDMETHODS FOR USE THEREWITH”, filed Dec. 6, 2022, all of which are herebyincorporated herein by reference in their entirety and made part of thepresent U.S. Utility patent application for all purposes.

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. § 120 as a continuation-in-part of U.S. Utility applicationSer. No. 17/819,016, entitled “GAME PLATFORM USING PLAYER TOKEN NFTS ANDMETHODS FOR USE THEREWITH”, filed Aug. 11, 2022, which claims prioritypursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No.63/364,568, entitled “NFT GAME PLATFORM WITH MULTIPLAYER SUPPORT ANDMETHODS FOR USE THEREWITH”, filed May 12, 2022; U.S. ProvisionalApplication No. 63/364,571, entitled “NFT GAME PLATFORM USING GAME TOKENNFTS AND METHODS FOR USE THEREWITH”, filed May 12, 2022; U.S.Provisional Application No. 63/364,573, entitled “NFT GAME PLATFORMUSING PLAYER TOKEN NFTS AND METHODS FOR USE THEREWITH”, filed May 12,2022; and U.S. Provisional Application No. 63/364,578, entitled “NFTGAME PLATFORM USING PLAYER TOKEN NFTS OR GAME TOKEN NFTS AND METHODS FORUSE THEREWITH”, filed May 12, 2022, all of which are hereby incorporatedherein by reference in their entirety and made part of the present U.S.Utility patent application for all purposes.

U.S. Utility application Ser. No. 17/819,016 also claims prioritypursuant to 35 U.S.C. § 120 as a continuation-in-part of U.S. Utilityapplication Ser. No. 17/806,766, entitled “SYSTEM FOR VALIDATING TICKETTRANSACTIONS VIA TICKET NFTS AND METHODS FOR USE THEREWITH”, filed Jun.14, 2022, which is a continuation-in-part of U.S. Utility applicationSer. No. 17/661,362, entitled “SYSTEM FOR VALIDATING PLAY OF GAMEAPPLICATIONS VIA GAME NFTS AND METHODS FOR USE THEREWITH”, filed Apr.29, 2022, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S.Provisional Application No. 63/362,581, entitled “SYSTEM FOR VALIDATINGPLAY OF GAME APPLICATIONS VIA GAME NFTS AND METHODS FOR USE THEREWITH”,filed Apr. 6, 2022, all of which are hereby incorporated herein byreference in their entirety and made part of the present U.S. Utilitypatent application for all purposes.

U.S. Utility application Ser. No. 17/661,362 also claims prioritypursuant to 35 U.S.C. § 120 as a continuation-in-part of U.S. Utilityapplication Ser. No. 17/656,084, entitled “FACILITATING PLAY OF GAMENFTS VIA A CLIENT DEVICE”, filed Mar. 23, 2022, which claims prioritypursuant to 35 U.S.C. § 119(e) to 35 U.S.C. § 119(e) to U.S. ProvisionalApplication No. 63/262,536, entitled “NFT COLLECTION PLATFORM ANDMETHODS FOR USE THEREWITH”, filed Oct. 14, 2021; U.S. ProvisionalApplication No. 63/262,762, entitled “NFT COLLECTION PLATFORM FORPROCESSING NFTS AND DATA AND METHODS FOR USE THEREWITH”, filed Oct. 20,2021; U.S. Provisional Application No. 63/262,858, entitled “NFTCOLLECTION PLATFORM FOR PROCESSING NFTS AND DATA AND METHODS FOR USETHEREWITH”, filed Oct. 21, 2021; U.S. Provisional Application No.63/263,844, entitled “NFT COLLECTION PLATFORM FOR RENDERING NFTS IN ANENVIRONMENT AND METHODS FOR USE THEREWITH”, filed Nov. 10, 2021; U.S.Provisional Application No. 63/264,811, entitled “CLIENT DEVICE FOR NFTSAND METHODS FOR USE THEREWITH”, filed Dec. 2, 2021; U.S. ProvisionalApplication No. 63/265,754, entitled “REAL ESTATE NFTS AND METHODS FORUSE THEREWITH”, filed Dec. 20, 2021; U.S. Provisional Application No.63/266,478, entitled “AUTHENTICATED LICENSE NFTS AND METHODS FOR USETHEREWITH”, filed Jan. 6, 2022; U.S. Provisional Application No.63/297,394, entitled “GENERATION OF ENHANCEMENT NFTS AND METHODS FOR USETHEREWITH”, filed Jan. 7, 2022; U.S. Provisional Application No.63/302,757, entitled “GENERATION OF NFT GALLERIES AND METHODS FOR USETHEREWITH”, filed Jan. 25, 2022; U.S. Provisional Application No.63/302,768, entitled “ENHANCEMENT OF REAL ESTATE NFTS VIA NFTGALLERIES”, filed Jan. 25, 2022; U.S. Provisional Application No.63/305,559, entitled “AUTHENTICATING NFT TRANSACTIONS VIA CONDITIONALNFTS”, filed Feb. 1, 2022; U.S. Provisional Application No. 63/305,505,entitled “GENERATING A SECURE REAL-TIME NFT REPOSITORY FORAUTHENTICATING NFT TRANSACTIONS”, filed Feb. 1, 2022; U.S. ProvisionalApplication No. 63/306,405, entitled “GENERATING NFTS WITH FRACTIONALRIGHTS IN ASSETS”, filed Feb. 3, 2022; U.S. Provisional Application No.63/306,412, entitled “GENERATING NFTS WITH FRACTIONAL RIGHTS IN ACOLLECTABLE”, filed Feb. 3, 2022; U.S. Provisional Application No.63/307,349, entitled “STREAMING OF VIDEO NFTS TO A CLIENT DEVICE”, filedFeb. 7, 2022; U.S. Provisional Application No. 63/308,546, entitled“NODE NFTS WITH TRANSACTION UPDATES”, filed Feb. 10, 2022; U.S.Provisional Application No. 63/309,382, entitled “GENERATING PLAYABLEGAME NFTS”, filed Feb. 11, 2022; and U.S. Provisional Application No.63/310,376, entitled “GENERATING UPDATED TEAM NFTS BASED ON TEAM DATA”,filed Feb. 15, 2022, all of which are hereby incorporated herein byreference in their entirety and made part of the present U.S. Utilitypatent application for all purposes.

U.S. Utility application Ser. No. 17/806,766 claims priority pursuant to35 U.S.C. § 119(e) to U.S. Provisional Application No. 63/365,010,entitled “SYSTEM FOR VALIDATING TICKET TRANSACTIONS VIA TICKET NFTS ANDMETHODS FOR USE THEREWITH”, filed May 19, 2022; and U.S. ProvisionalApplication No. 63/365,012, entitled “METHOD AND SYSTEM FORAUTHENTICATING TICKET NFT TRANSACTIONS IN REALTIME”, filed May 19, 2022,both of which are hereby incorporated herein by reference in theirentirety and made part of the present U.S. Utility patent applicationfor all purposes.

TECHNICAL FIELD

The present disclosure relates to processing systems and applicationsused in the collection, generation, display and use of non-fungibletokens (NFTs) or other digital tokens.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A presents a block diagram representation of an example system.

FIG. 1B presents a block diagram representation of an examplenon-fungible token (NFT) collection platform.

FIG. 2 presents a block diagram representation of an example clientdevice.

FIG. 3A presents a flowchart representation of an example method.

FIGS. 3B-3F and 3H present pictorial representations of example screendisplays.

FIG. 3G presents a flow diagram representation of an example process.

FIG. 3I presents a flowchart representation of an example method.

FIG. 4A presents a flowchart representation of an example method.

FIG. 4B presents a pictorial representation of an example screendisplay.

FIG. 4C presents a flow diagram representation of an example process.

FIG. 5A presents a flowchart representation of an example method.

FIGS. 5B and 5C present pictorial representations of example screendisplays.

FIG. 6 presents a block diagram/flow representation of an example of NFTgeneration.

FIG. 7 presents a block diagram representation of an example system.

FIG. 8 presents a block diagram representation of an example clientdevice.

FIG. 9A presents a block diagram/flow representation of an example ofNFT generation.

FIG. 9B presents a pictorial representation of an example NFT.

FIG. 9C presents a pictorial representation of an example improvement.

FIG. 9D presents a pictorial representation of an example NFT.

FIG. 9E presents a flowchart representation of an example method.

FIG. 10A presents a block diagram/flow representation of an example ofNFT generation.

FIG. 10B presents a flowchart representation of an example method.

FIG. 11A presents a block diagram/flow representation of an example ofNFT generation.

FIG. 11B presents a pictorial representation of an example NFT.

FIG. 11C presents a pictorial representation of example enhancements.

FIG. 11D presents a pictorial representation of an example NFT.

FIG. 11E presents a flowchart representation of an example method.

FIG. 12A presents a block diagram of an example system.

FIG. 12B presents a flowchart representation of an example method.

FIG. 12C presents a pictorial block diagram/flow representation of anexample of transaction authentication.

FIG. 12D presents a flowchart representation of an example method.

FIG. 13A presents a pictorial representation of an example NFT.

FIG. 13B presents a flowchart representation of an example method.

FIG. 13C presents a pictorial representation of an example screendisplay.

FIG. 13D presents a pictorial/block diagram representation of an examplesystem with screen display.

FIG. 13E presents a flowchart representation of an example method.

FIG. 13F presents a block diagram/flow representation of an example ofNFT generation.

FIG. 13G presents a pictorial representation of an example NFT.

FIG. 13H presents a pictorial/flow representation of an example updateto an NFT.

FIG. 13I presents a flowchart representation of an example method.

FIG. 13J presents a block diagram/flow representation of an example ofNFT generation.

FIG. 13K presents a pictorial representation of an example derivativeNFT.

FIG. 13L presents a pictorial representation of an example clientdevice.

FIG. 13M presents a block diagram/flow representation of an example ofNFT generation.

FIG. 13N presents a flowchart representation of an example method.

FIG. 13O presents a flowchart representation of an example method.

FIG. 13P presents a flowchart representation of an example method.

FIG. 13Q presents a flowchart representation of an example method.

FIG. 14A presents a block diagram representation of an example system.

FIG. 14B presents a block diagram representation of an example system.

FIG. 14C presents a block diagram representation of an example system.

FIG. 14D presents a block diagram representation of an example system.

FIG. 14E presents a block diagram representation of an example system.

FIG. 14F presents a block/flow diagram representation of an examplesystem.

FIG. 14G presents a flowchart representation of an example method.

FIG. 14H presents a flowchart representation of an example method.

FIG. 14I presents a flowchart representation of an example method.

FIG. 14J presents a flowchart representation of an example method.

FIG. 14K presents a flowchart representation of an example method.

FIG. 14L presents a flowchart representation of an example method.

FIG. 14M presents a flowchart representation of an example method.

FIG. 14N presents a flowchart representation of an example method.

FIG. 15A presents a block diagram representation of an example system.

FIGS. 15B-15J present pictorial representations of example screendisplays.

FIG. 15K presents a block/flow diagram representation of an examplesystem.

FIG. 15L presents a flowchart representation of an example method.

FIG. 15M presents a block/flow diagram representation of an examplesystem.

FIG. 15N presents a flowchart representation of an example method.

FIG. 15O presents a flowchart representation of an example method.

FIG. 15P presents a flowchart representation of an example method.

FIG. 15Q presents a flowchart representation of an example method.

FIG. 15R presents a flowchart representation of an example method.

FIG. 16A presents a block diagram representation of an example system.

FIG. 16B presents a flowchart representation of an example method.

FIG. 16C presents a block/flow diagram representation of an examplesystem.

FIG. 16D presents a pictorial/flow diagram representation of an exampleprocess.

FIG. 16E presents a flowchart representation of an example method.

FIG. 16F presents a block/flow diagram representation of an examplesystem.

FIG. 16G presents a pictorial/flow diagram representation of an exampleprocess.

FIG. 16H presents a flowchart representation of an example method.

FIGS. 16I-16J present a block/flow diagram representations of examplesystems.

FIG. 16K presents a flowchart representation of an example method.

FIG. 16L presents a block/flow diagram representation of an examplesystem.

FIG. 16M presents a flowchart representation of an example method.

FIG. 17A presents a pictorial representation of an example screendisplay.

FIG. 17B presents a block diagram representation of an example system.

FIG. 17C presents a flowchart representation of an example method.

FIG. 17D presents a block/flow diagram representation of an examplesystem.

FIG. 17E presents a pictorial/flow diagram representation of an exampleprocess.

FIG. 17F presents a flowchart representation of an example method.

FIG. 17G presents a block/flow diagram representation of an examplesystem.

FIG. 17H presents a pictorial/flow diagram representation of an exampleprocess.

FIG. 17I presents a flowchart representation of an example method.

FIGS. 17J-17K present a block/flow diagram representations of examplesystems.

FIG. 17L presents a flowchart representation of an example method.

FIG. 17M presents a block/flow diagram representation of an examplesystem.

FIG. 17N presents a flowchart representation of an example method.

FIG. 18A presents a block/flow diagram representation of an examplesystem.

FIG. 18B presents a flowchart representation of an example method.

FIGS. 18C-18D present a block/flow diagram representations of examplesystems.

FIG. 18E presents a flowchart representation of an example method.

FIG. 18F presents a block/flow diagram representation of an examplesystem.

FIG. 18G presents a flowchart representation of an example method.

FIG. 18H presents a block/flow diagram representation of an examplesystem.

FIG. 18I presents a flowchart representation of an example method.

FIG. 18J presents a flowchart representation of an example method.

FIG. 18K presents a flowchart representation of an example method.

FIGS. 18L-18M present a block/flow diagram representations of examplesystems.

FIG. 18N presents a flowchart representation of an example method.

FIGS. 18O-18P present a block/flow diagram representations of examplesystems.

FIG. 18Q presents a flowchart representation of an example method.

FIG. 18R presents a flowchart representation of an example method.

FIG. 19A presents a pictorial diagram representation of an example item.

FIG. 19B presents a pictorial diagram representation of an exampleclient device.

FIG. 19C presents a flowchart representation of an example method.

FIG. 20A presents a pictorial diagram representation of an example item.

FIG. 20B presents a pictorial diagram representation of an example item.

FIG. 20C presents a pictorial diagram representation of an exampleclient device.

FIG. 20D presents a pictorial diagram representation of an exampleclient device.

FIG. 20E presents a flowchart representation of an example method.

FIG. 20F presents a flowchart representation of an example method.

FIG. 20G presents a flowchart representation of an example method.

FIG. 20H presents a flowchart representation of an example method.

FIG. 21A presents a block diagram representation of an example system.

FIG. 21B presents a pictorial block/flow diagram representation of anexample system.

FIG. 21C presents a flowchart representation of an example method.

DETAILED DESCRIPTION

FIG. 1A presents a block diagram representation of an example system inaccordance with various examples. In particular, a system 850 ispresented that includes an NFT collection platform 800 that communicateswith client devices 825 via a network 115. The network 115 can be theInternet or other wide area or local area network, either public orprivate. The client devices 825 can be computing devices such aslaptops, smartphones, smart watches, tablets, desktops, or othercomputing devices associated with users, for example, buyers, sellers,collectors and/or users of NFTs.

NFT creation and ownership is growing worldwide. Existing platformsprovide tools to create NFTs, marketplaces for buying and selling NFTsand wallets to securely hold them. Many NFT purchasers however, viewNFTs similarly to cryptocurrency, purely as financial investments to becollected and later sold. Unlike cryptocurrencies which are fungibletokens, NFTs have a non-fungible (e.g. unique or limited) component thatcan correspond to photographs, graphics, art, video, games or othermedia or imagery that can be displayed, used in authentication and/or toprovide other support for transactions and/or used in game play and forother utilitarian purposes, etc.

In the example shown, the NFT collection platform 800 includes a clientdevice interface 802 for interacting with the client devices 825, NFTmarketplace tools 804, NFT wallet tools 806, NFT generation tools 808,NFT collection display tools 810, one or more games 812 that can beplayed using NFTs that have been collected including game NFTs thatinclude and/or otherwise associated with, or correspond to, playablegame content, and a database 814 for storing user and accountinformation, preferences, display settings and other data associatedwith users of the NFT collection platform 800. The NFT collectionplatform 800 can include or be implemented via one or more servers, acloud computing system, an InterPlanetary File System (IPFS) or otherdecentralized or distributed computer system of individual computersand/or nodes and/or a centralized computing system.

For example, the client device interface 802 can operate in conjunctionwith each client device 825 and via network 115 to generate a graphicaluser interface. This graphical user interface is based on display datagenerated by the NFT collection platform 800 in a format for display ona display device associated with the client devices 825. This graphicaluser interface generates input data that is received by the NFTcollection platform 800 from the client devices 825 in response to userinteraction with the graphical user interface.

In various examples, the NFT collection platform 800 can serve the needsof a collector of NFTs by providing a system that offers new experiencesthat support various collector and/or use behaviors in the NFT world andmetaverse including the collection, display, and use of NFTs and theircorresponding content. The NFT collection display tools 810 can includea high-fidelity customizable page builder so each collector canpersonalize and display their NFTs in an environment. The NFT collectionplatform 800 can provide and support a collection social media sitethat, for example, is similar to MySpace, Facebook, or OnlyFans, butspecifically directed to the arrangement, posting, sharing and/ordisplay of collections of NFTs.

In the most basic mode of operation, the NFT collection platform 800improves the technology of NFT systems by allowing the user to collect,arrange and display NFTs they have purchased so that the user, and otherusers, can enjoy and admire the NFTs they have collected. The NFTcollection platform 800 not only allows users to curate, display and usetheir collections, to play games associated with their NFTs and/or alsoallows users to create a social/professional profile of their NFTproperty—enabling users to get creative with how their collections arepresented, used and displayed. In addition, when a group of NFTs iscollected and/or when a personalized/curated collection page, set and/orcollection display is built, the NFT collection platform 800 improvesthe technology of NFT systems by allowing the user to mint a new“collection NFT” using blockchain-based, distributed computer network,and/or other crypto-based NFT creation techniques, for example andauthenticated based on the user's ownership of the underlying NFTs.

Furthermore, the NFT collection platform 800 allows users to buy, sell,loan, borrow and trade NFTs with other users, including their owncollection NFTs created based on their own collections. In variousexamples, the NFT collection platform 800 may not include a NFT creator,marketplace or wallet itself. The NFT generation tools 808, NFT wallettools 806 and NFT marketplace tools 804 can reside on the NFT collectionplatform 800 and interface with one or more NFT wallet systems 820, NFTmarketplaces 822 and/or NFT creation systems 824 to enabletransactions/interactions/abilities at a metaverse level, offeringcollectors new and unique experiences, pre and post purchase, across alldifferent NFT's and blockchains in one place. The NFT collectionplatform 800 improves the technology of NFT systems by allowing the userto perform the functions above in a fashion, that can be blockchain,wallet, and marketplace agnostic.

It should be noted that the system 850 can operate via blockchain-basedtechnologies. In blockchain, a growing list of records, called “blocks”,are linked together using cryptography and spread over a decentralizedcomputer system/network or other distributed network of participants.Each block contains a cryptographic hash of the previous block, atimestamp, and transaction data (generally represented as a Merkletree). The timestamp proves that the transaction data existed when theblock was published in order to get into its hash. As blocks eachcontain information about the block previous to it, they form a chain,with each additional block reinforcing the ones before it. Therefore,blockchains are resistant to modification of their data because oncerecorded, the data in any given block cannot be altered retroactivelywithout altering all subsequent blocks. The distributed nature of thisprocess over different nodes, the contemporaneous nature ofgeographically distinct calculations, coupled with the extremecomputational complexity of the required calculations means that theseblockchain-based technologies cannot practically be performed by thehuman mind.

It should be noted, that while the NFT wallet system 820, NFTmarketplace 822 and NFT creation system 824 are shown as separateentities and as being external to the NFT collection platform 800, otherconfigurations are possible where two or more of these entities share acommon platform and/or the functions and features of one or more ofthese entities can be incorporated within the NFT collection platform800 itself.

It should also be noted that while client device interface 802, NFTmarketplace tools 804, NFT wallet tools 806, NFT generation tools 808,NFT collection display tools 810, games 812 and database 814 are shownas being internal to the NFT collection platform 800, in other examples,any subset of the various elements of the NFT collection platform 800can be implemented external to the NFT collection platform 800 andcoupled to the other components via the network 115. Furthermore, theNFT collection platform 800 can be implemented in a cloud computingconfiguration with any or all of the various elements of the NFTcollection platform 800 implemented within the cloud.

The further operation of this system will be described in greater detailin conjunction with the figures that that follow, including manyoptional functions and features and examples thereof.

FIG. 1B presents a block diagram representation of an NFT collectionplatform 800 in accordance with various examples. In particular, the NFTcollection platform 800 includes a network interface 820 such as a 3G,4G, 5G or other cellular wireless transceiver, a Bluetooth transceiver,a WiFi transceiver, UltraWideBand transceiver, WIMAX transceiver, ZigBeetransceiver or other wireless interface, a Universal Serial Bus (USB)interface, an IEEE 1394 Firewire interface, an Ethernet interface orother wired interface and/or other network card or modem forcommunicating for communicating via the network 115.

The NFT collection platform 800 also includes a processing module 830and memory module 840 that stores an operating system (O/S) 844 such asan Apple, Unix, Linux or Microsoft operating system or other operatingsystem, client device interface 802, NFT marketplace tools 804, NFTwallet tools 806, NFT generation tools 808, NFT collection display tools810, games 812 and database 814. In particular, the O/S 844, the clientdevice interface 802, NFT marketplace tools 804, NFT wallet tools 806,NFT generation tools 808, NFT collection display tools 810, and games812 each include operational instructions that, when executed by theprocessing module 830, cooperate to configure the processing module 830into a special purpose device to perform the particular functions of theNFT collection platform 800 described herein.

The NFT collection platform 800 may include a user interface (I/F) 862such as a display device, touch screen, key pad, touch pad, joy stick,thumb wheel, a mouse, one or more buttons, a speaker, a microphone, anaccelerometer, gyroscope or other motion or position sensor, videocamera or other interface devices that provide information to anadministrator of the NFT collection platform 800 and that generate datain response to the administrator's interaction with NFT collectionplatform 800.

The processing module 830 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, quantum computing device, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on operationalinstructions that are stored in a memory, such as memory 840. The memorymodule 840 can include a hard disc drive or other disc drive, read-onlymemory, random access memory, volatile memory, non-volatile memory,static memory, dynamic memory, flash memory, cache memory, and/or anydevice that stores digital information. Note that when the processingdevice implements one or more of its functions via a state machine,analog circuitry, digital circuitry, and/or logic circuitry, the memorystoring the corresponding operational instructions may be embeddedwithin, or external to, the circuitry comprising the state machine,analog circuitry, digital circuitry, and/or logic circuitry. While aparticular bus architecture is presented that includes a single bus 860,other architectures are possible including additional data buses and/ordirect connectivity between one or more elements. Further, the NFTcollection platform 800 can include one or more additional elements thatare not specifically shown.

FIG. 2 presents a block diagram representation of an example clientdevice in accordance with various examples. In particular, a clientdevice 825 is presented that includes a network interface 220 such as a3G, 4G, 5G or other cellular wireless transceiver, a Bluetoothtransceiver, a WiFi transceiver, UltraWideBand transceiver, WIMAXtransceiver, ZigBee transceiver or other wireless interface, a UniversalSerial Bus (USB) interface, an IEEE 1394 Firewire interface, an Ethernetinterface or other wired interface and/or other network card or modemfor communicating for communicating via network 115.

The client device 825 also includes a processing module 230 and memorymodule 240 that stores an operating system (O/S) 244 such as an Apple,Unix, Linux or Microsoft operating system or other operating system, NFTdata 246 associated with one or more NFTs owned by the user, and/or acollection applications 248. In particular, the O/S 244 and collectionapplication 248 each include operational instructions that, whenexecuted by the processing module 230, cooperate to configure theprocessing module into a special purpose device to perform theparticular functions of the client device 825 described herein.

The client device 825 also includes a user interface (I/F) 262 such as adisplay device, touch screen, key pad, touch pad, joy stick, thumbwheel, a mouse, one or more buttons, a speaker, a microphone, anaccelerometer, gyroscope or other motion or position sensor, videocamera or other interface devices that provide information to a user ofthe client device 825 and that generate data in response to the user'sinteraction with the client device 825.

The processing module 230 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, quantum computing device, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on operationalinstructions that are stored in a memory, such as memory 240. The memorymodule 240 can include a hard disc drive or other disc drive, read-onlymemory, random access memory, volatile memory, non-volatile memory,static memory, dynamic memory, flash memory, cache memory, and/or anydevice that stores digital information. Note that when the processingdevice implements one or more of its functions via a state machine,analog circuitry, digital circuitry, and/or logic circuitry, the memorystoring the corresponding operational instructions may be embeddedwithin, or external to, the circuitry comprising the state machine,analog circuitry, digital circuitry, and/or logic circuitry. While aparticular bus architecture is presented that includes a single bus 260,other architectures are possible including additional data buses and/ordirect connectivity between one or more elements. Further, the clientdevice 825 can include one or more additional elements that are notspecifically shown.

The client device 825 operates, via network interface 220, network 115and NFT collection platform 800. In various examples, the client device825 operates to display a graphical user interface generated based ondisplay data from the NFT collection platform 800, includingcorresponding screen displays. Furthermore, the graphical user interfacecan operate in response to interactions by a user to generate input datathat is sent to the NFT collection platform 800 to control the operationof the NFT collection platform 800 and/or to provide other input.

It should be noted that while the client devices 825 and NFT collectionplatform 800 are shown as separate devices that communicate via thenetwork 115, it should be noted that any and all of the functionalityattributed to the NFT collection platform 800, including the NFTmarketplace tools 804, NFT wallet tools 806, NFT generation tools 808,NFT collection display tools 810, games 812, and database 814, etc. canlikewise be incorporate directly into the client device 825. In thisfashion, a client device 825 through the application of its operatingsystem 244 and one or more applications can provide a graphical userinterface to operate via network 115 but independently from any NFTcollection platform to perform any of the functions and featuresdescribed herein. In particular, the client device 825 can perform thefunctions of both the client device and the NFT collection platform 800without requiring communications to be sent to the client device 825from a NFT collection platform and communications sent to a NFTcollection platform from the client device 825.

FIG. 3A presents a flowchart representation of an example method inaccordance with various examples. In particular, a method 300 for use inconjunction with any of the functions and features described herein forgenerating a collection NFT based on NFTs in a user's collection.

Step 302 includes importing, via a network interface, a plurality ofNFTs associated with the user of the client device. Step 304 includesgenerating, via a processor and in response to user interactions withthe graphical user interface, display data associated with a customizedcollection display that contains the plurality of NFTs. Step 306includes sending, via the network interface, the display data associatedwith the customized collection display via the client device of theuser. Step 308 includes facilitating creation of a collection NFTcorresponding to the customized collection display that contains theplurality of NFTs.

FIGS. 3B-3F and 3H present pictorial representations of example screendisplays. In particular, screen displays of a graphical user interfacegenerated based on display data from the NFT collection platform 800 areshown. In the example below, three NFTs are used to design and create anew collection NFT based on a common theme, the 1999 Chicago Bulls teamin the National Basketball association.

In FIG. 3B, the user “Bruce Stuckman” is logged into the NFT collectionplatform 800. The user has interacted with NFT wallet tools, such as NFTwallet tools 804, to import NFTs 100 and 102 from his wallet residing inNFT wallet system 820. In this example, the NFTs 100 and 102 areblockchain authenticated original photographs depicting two differentimages of the 1999 Chicago Bulls.

In FIG. 3C, the user has interacted with the NFT marketplace tools, suchas NFT marketplace tools 804, to select a new NFT 104 for purchase viaan NFT marketplace such as NFT marketplace 822. In FIG. 3D, the wallettools are used again, this time to export the NFT 104 to the user'swallet. In FIG. 3E, the user has selected and used NFT collectiondisplay tools, such as NFT collection display tools 810, to create acustomized collection display 110 contain all three 1999 ChicagoBulls-related NFTs he now owns. In the example shown, the user has“dragged and dropped” NFTs he owns in a custom display window and hassized and arranged them into the particular collage that is shown. Inother examples, the NFT collection display tools 810 can operate, basedon metadata associated with the NFTs of a user indicating content,theme, color themes, subject matter, dates of creation, authorship,ownership, prior ownership, number of prior owners, size, resolution,and other NFT information and metadata, to automatically generatearrangements of custom collection display 110 that may be accepted bythe user and/or that may be further arranged by the user to create thefinal customized collection display 110.

In FIG. 3F, the user has selected NFT generation tools, such as NFTgeneration tools 808, in order to facilitate, via NFT creation system824 for example, the creation of a collection NFT from the customizedcollection display 110.

FIG. 3G presents a flow diagram representation of an example process. Inthe example shown, the collection NFT 120 is created from the customizedcollection display 110. As previously discussed, the NFT generationtools can operate by, for example, first authenticating the user'srights in the three NFTs and then creating, via NFT creation system 824,a new NFT of the unique customized image with its own blockchainauthentication. In various examples, the collection NFT 120 can containmetadata indicating, for example attributions to the sources of theoriginal NFTs in the collection, the creator of the collection NFT, adate of creation, promotion data and coupons related to offers,privileges and/or discounts, title data with respect to title totangible or intangible real or personal property, warrant data withrespect to tangible or intangible real or personal property, transactiondata regarding one or more transactions, and/or other metadata. Thismetadata can be protected via the blockchain and/or other crypto-basedNFT creation technology that is employed to create and protect thecollection NFT itself—with or without associated image data. In FIG. 3H,the wallet tools are used again, this time to export the collection NFT120 to the user's wallet.

FIG. 3I presents a flowchart representation of an example method inaccordance with various examples. In particular, a method 310 ispresented for use in conjunction with any of the functions and featuresdescribed herein for generating a collection NFT based on NFTs in auser's collection.

Step 312 includes importing, via a network interface, a plurality ofNFTs associated with the user of the client device. Step 314 includesgenerating, via a processor and in response to metadata associated withthe plurality of NFTs, display data associated with a customizedcollection display that contains the plurality of NFTs. Step 316includes sending, via the network interface, the display data associatedwith the customized collection display via the client device of theuser. Step 318 includes facilitating creation of a collection NFTcorresponding to the customized collection display that contains theplurality of NFTs.

FIG. 4A presents a flowchart representation of an example method. Inparticular, a method 400 for use in conjunction with any of thefunctions and features described herein in generating a collection NFTbased on at least one NFT accessed via a temporary micro-loan.

Step 402 includes facilitating, via a processor and in response to userinteractions with the graphical user interface, a temporary micro-loanof at least one NFT. Step 404 includes generating, via the processor andin response to user interactions with the graphical user interface,display data associated with a customized collection display thatcontains a plurality of NFTs including the at least one NFT. Step 406includes sending, via the network interface, the display data associatedwith the customized collection display via the client device of theuser. Step 408 includes facilitating creation of a collection NFTcorresponding to the customized collection display that contains theplurality of NFTs including the at least one NFT.

FIG. 4B presents a pictorial representation of an example screendisplay. In particular, the user has used the marketplace tools toselect NFTs 100-1, 102-1, and 104-1. Instead of putting these NFTs upfor purchase, the original owners have made them available for temporarymicro-loan. This process allows the users can engage to, in exchange fora fee, “borrow” NFTs in order to create a collection NFT. After theCollection NFT is created, or upon the expiration of some predeterminedtime period (such as 15 minutes, 30 minutes, an hour, a day, etc.) themicro-loaned NFT(s) are returned, expire, deleted or destroyed.Transaction fees apply, a portion of which can be credited to theoriginal NFT owner, the author, including an upfront cost, reward-basedpayment based on the use and/or performance of the micro-loaned NFT etc.In the alternative, a fixed fee could be charged to the user andcredited to the original NFT owner. In various examples, the NFTcollection platform 800 may be configured to operate with a single userand/or within a single wallet, and/or to otherwise prohibit the sale orborrowing of micro-loaned NFTs to avoid dilution of the value of theoriginal itself. Furthermore, original and/or derivative NFTs caninclude restrictions on the total number of micro-loan transactions, thenumber of simultaneous/contemporaneous micro-loans, restrictions ontypes of microloan transactions such as normal use loans, staking loans,death match loans, loans less than a predetermined length of time, loansgreater than a predetermined length of time, etc.

Consider the following example where an NFT is put up for loan. Theproposed loan transaction can include restrictions including anexpiration time and/or date, one or N time use in creating a collectionNFT or in a game, tournament or challenge, etc. Once the loan isaccepted by the borrower, an additional NFT, such as a derivative NFT ofthe original NFT being loaned, is created on a side chain, layer 1 or 2blockchain (or “parachain”) that can be different from (and/orindependent from) the blockchain used to create the original NFT. Thisnew NFT can be created and transferred to the wallet of the borrower viaa smart contract that is based on the restrictions. A cryptocurrencymarket can be used to fund the transaction and/or to collateralize themicro-loan. The new NFT can then be set via the smart contract toautomatically expire (e.g. be deleted from the wallet, destroyed orotherwise disabled), when the restrictions are met. In this fashion, ifthe purpose of the micro-loan is the creation of a collection NFT, theborrowed NFT can automatically expire once the collection NFT iscreated. It should be noted that the collection NFT can be created viathe same blockchain platform (e.g. Ethereum) used to create the originalNFT (e.g. not the parachain).

FIG. 4C presents a flow diagram representation of an example processwhere a collection NFT 120-1 is generated based on a customizedcollection display 110-1 created by the user based on the borrowed NFTs100-1, 102-1 and 104-1. In various examples, the collection NFT 120-1metadata can also indicate the original sources of the micro-loans aswell as the micro-loaned status of NFTs 100-1, 102-1 and 104-1. Whilenot expressly shown, the collection NFTs based on one or moremicro-loaned NFTs, can be created with a visual indication of theoriginal vs. micro-loaned status of the NFTs as appropriate.

FIG. 5A presents a flowchart representation of an example method. Inparticular, a method 1300 for use in conjunction with any of thefunctions and features previously described facilitates the collectionof endorsements associated with an NFT. Step 1302 includes importing,via a network interface, an NFT associated with the user of the clientdevice. Step 1304 includes collecting, via a processor and in responseto user interactions with the graphical user interface, endorsement dataassociated with the NFT. Step 1306 includes generating, via theprocessor and in response to user interactions with the graphical userinterface, display data associated with a customized collection displaythat contains the NFT and the endorsement data. Step 1308 includessending, via the network interface, the display data associated with thecustomized collection display via the client device of the user. Step1310 includes facilitating creation of a collection NFT corresponding tothe customized collection display.

FIGS. 5B and 5C present pictorial representations of example screendisplays. In FIG. 5B, the user is interacting with the graphical userinterface to use the NFT marketplace tools to seek an endorsement for aselected NFT. After an endorsement in the form of a signature has beenreceived it can be appended to the customized collection display of theNFT. In FIG. 5C, the user interacts with the NFT generation tools togenerate a collection NFT that includes both the NFT and the signature.In various examples, this collection NFT 120-6 metadata can alsoindicate an attribution associated the endorsement itself. Furthermore,the endorsement itself can be an original NFT, a derivative NFT, amicro-loaned NFT or other NFT.

FIG. 6 presents a block diagram/flow representation of an example of NFTgeneration. In the example shown, NFT generation tools 808 operate toconvert display data 1502 and other data 1504 into an NFT 1506. Thedisplay data 1502 can correspond to an original NFT, borrowed (e.g.temporary micro-loaned) NFT, a derivative NFT, a customized collectiondisplay 110, an original image, and/or other derivatives or micro-loansthereof or other display or image data. In various examples, the NFTgeneration tools 808 can operate to verify the credentials of any NFTswhose images are contained in the display data 1502, prior to creatingthe NFT 1506. In this fashion, derivative NFTs can only be created whenthe source NFT or NFTs are verified—preventing the creation ofunauthorized or counterfeit NFTs.

The other data 1504, can be image data including signatures and otherendorsement images, visual indications of derivative series, originalityclassification, attributions, or other image data, metadata of all kindsincluding metadata indicating one or more originality classifications,attributions, endorsement data, other derivative data indicating theseries number and total number in a derivative series, restrictions onmicro-loans or other derivatives, restrictions on derivatives withartistic effects, restrictions that derivatives must includeattributions to the original source, restrictions on numbers ofderivatives or micro-loans or the sizes of derivative series,restrictions on the creation of collection NFTs, the number ofcollection NFTs, the creation of collection NFTs including NFTs fromother sources, from prohibited sources or with prohibited content,geographical restrictions, time restrictions (e.g., can be used tocreate derivatives or collection NFTs or can be temporarily micro-loanedfor 1 month, one year, etc., other restrictions and/or other dataassociated with, or to be associated with, the display data 1502.

This other data 1504 can be used to generate an NFT and/or combined withthe display data 1502 to create a dataset that includes both the displaydata 1502 and the other data 1504. This other data 1504 or combineddataset can be protected via the blockchain and/or other crypto-basedNFT creation technology that is employed by the NFT generation tools 808and via the NFT creation system 824 to create and protect the new NFT1506 itself. It should be noted that the NFT 1506 can include a singlederivative or a number of derivatives, including a limited series ofderivatives. It should be noted further that some or all of the otherdata 1504, including restriction data and/or attribution data, can bederived from one or more original NFTs whose images are associated withthe display data 1502. Furthermore, some or all of the other data 1504can be generated in response to user interactions with a graphical userinterface generated in conjunction with the NFT collection platform 800.

FIG. 7 presents a block diagram representation of an example system. Inparticular, a system 2850 is presented that includes an NFT distributionplatform 2800 that communicates with client devices 825 via a network115. The network 115 can be the Internet or other wide area or localarea network, either public or private. The client devices 825 can becomputing devices associated with users, for example, buyers, sellers,collectors, game players and/or other users of NFTs.

In the example shown, the NFT distribution platform 2800 includes aclient device interface 2802 for interacting with the client devices825, NFTs 2804 to be distributed, and an operating system 2844. One ormore of the NFTs 2804 can have geographical restrictions as todistribution that are either part of the NFTs themselves or haverestriction data that is stored separately.

The NFT distribution platform 2800 includes a network interface 2820such as a 3G, 4G, or another cellular wireless transceiver, a Bluetoothtransceiver, a WiFi transceiver, UltraWideBand transceiver, WIMAXtransceiver, ZigBee transceiver or other wireless interface, a UniversalSerial Bus (USB) interface, an IEEE 1394 Firewire interface, an Ethernetinterface or other wired interface and/or other network card or modemfor communicating for communicating via the network 115.

The NFT distribution platform 2800 also includes a processing module2830 and memory module 2840 that stores an operating system (O/S) 2844such as an Apple, Unix, Linux or Microsoft operating system or anotheroperating system, the client device interface 2802, and the NFTs 2804.The O/S 2844 and the client device interface 802 each includeoperational instructions that, when executed by the processing module830, cooperate to configure the processing module 830 into a specialpurpose device to perform the particular functions of the NFTdistribution platform 2800 described herein.

The NFT distribution platform 2800 may include a user interface (I/F)2862 such as a display device, touch screen, key pad, touch pad, joystick, thumb wheel, a mouse, one or more buttons, a speaker, amicrophone, an accelerometer, gyroscope or other motion or positionsensor, video camera or other interface devices that provide informationto an administrator of the NFT distribution platform 2800 and thatgenerate data in response to the administrator's interaction with NFTdistribution platform 2800.

The processing module 2830 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, quantum computing device, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on operationalinstructions that are stored in a memory, such as memory 2840. Thememory module 2840 can include a hard disc drive or other disc drive,read-only memory, random access memory, volatile memory, non-volatilememory, static memory, dynamic memory, flash memory, cache memory,and/or any device that stores digital information. Note that when theprocessing device implements one or more of its functions via a statemachine, analog circuitry, digital circuitry, and/or logic circuitry,the memory storing the corresponding operational instructions may beembedded within, or external to, the circuitry comprising the statemachine, analog circuitry, digital circuitry, and/or logic circuitry.While a particular bus architecture is presented that includes a singlebus 2860, other architectures are possible including additional databuses and/or direct connectivity between one or more elements. Further,the NFT distribution platform 2800 can include one or more additionalelements that are not specifically shown.

For example, the client device interface 2802 can operate in conjunctionwith each client device 825 and via network 115 to generate a graphicaluser interface. This graphical user interface is based on display datagenerated by the NFT distribution platform 2800 in a format for displayon a display device associated with the client devices 825. Thisgraphical user interface generates input data that is received by theNFT distribution platform 2800 from the client devices 825 in responseto user interaction with the graphical user interface.

In various examples, the NFT distribution platform 2800 can operate torespond to input data from client devices in the form of read requestsfor NFTs and geolocation data such as GPS coordinates, connection to orproximity with a network element of network 115 or other location dataindicating a location of the client device 825. The NFT distributionplatform 2800 sends the requested NFT(s) to the requesting clientdevice—only when the geolocation data conforms with restriction data—forexample, when the geolocation data indicates a position of therequesting client device within a limited area or proximity indicated bythe restriction data.

FIG. 8 presents a block diagram representation of an example clientdevice. In particular, a client device 825-1 is presented that functionssimilarly to client device 825, and includes several elements of clientdevice 825 that are referred to by common reference numerals. The clientdevice 825-1 is capable of operating to client device 825 describedherein.

In addition, the memory module 240 includes a wallet application (app)250 that is capable of engaging in financial transactions includingcredit card transactions and traditional digital payments, is capable ofholding crypto-currency and engaging in crypto-currency transactions andis further capable of storing one or more NFTs that are either originalNFTs, derivative NFTs, borrowed (temporarily micro-loaned) NFTs,collection NFTs and/or combinations thereof. In various examples, thewallet app 250 is capable of operating in conjunction with the NFTcollection platform 800, the NFT distribution platform 2800, the NFTwallet system 820, the NFT marketplace 822, and/or the NFT creationsystem 824 via network 115.

As will be understood by one skilled in the art, unlike a normal wallet,which can physically hold cash, credit cards, etc., NFT wallets “store”NFTs by storing the NFT data necessary to access the NFT. So, eventhough a wallet can be said to store an NFT, technically the NFT contentis stored on the blockchain, which can only be accessed via the NFT datain the wallet. This NFT data includes metadata, other off-chain datacorresponding to the NFT and in particular, a private key. This privatekey can be considered an indicator of ownership of the NFT and isrequired to access the NFT via the blockchain. If the NFT data(including the private key) is lost, the NFT can no longer beaccessed—and the NFT is itself “lost” for all intents and purposes, eventhough it remains immutably stored on the blockchain.

Also, the memory module 240 includes one or more game apps 252 thatrepresent either stand alone games of the client device 825-1 or thatoperate in conjunction with the games 812 of the NFT collection platform800 and/or interface with the NFT distribution platform 2800. Thisallows, for example, a user of client device 825-1 to engage in (e.g.play) games associated with NFT content, and engage in other activitiesthat involve the acquisition, collection, display, distribution, and/oruse of one or more NFTs that are either original NFTs, derivative NFTs,borrowed (temporarily micro-loaned) NFTs, collection NFTs and/orcombinations thereof.

Furthermore, the network interface 220 includes one more geolocationselements 222 such as a GPS receiver, a ultra-wideband (UWB) transceiver,a Bluetooth transceiver and/or other component(s) that that facilitatethe generation of geolocation data and/or facilitate otherlocation-based services. Consider the case where the client device 825is a smartphone or tablet and the wallet app 250 is an Apple or Androidwallet or mobile wallet card that is in a Apple or Android wallet. Oncethe wallet app 250 is activated, NFTs can be easily added to the wallet.In addition, the wallet app 250 can access the location services of thedevice, and for example, generate push notifications regarding NFTs thatare available near the current location.

In various examples, the geolocation data generating in such a fashioncan facilitate the generation of geolocation data discussed inconjunction with the operation of NFT distribution platform 2800. Inparticular, the NFT distribution platform 2800 can automatically detectthe presence of the user at a venue based on geolocation data receivedfrom the user's client device 825-1 and automatically prompted the userto click to send a read request. In this fashion, the user can begeo-authorized, before the request. In other examples, the NFTdistribution platform 2800 can distribute NFTs to client devices 825based on payments, authentication and/or other criteria that does notrely on geolocation data.

Furthermore, while the client device 825-1 and NFT collection platform800 (or NFT distribution platform) are shown as separate devices thatcommunicate via the network 115, it should be noted that any and all ofthe functionality attributed to the NFT collection platform 800 (or NFTdistribution platform), including the NFT marketplace tools 804, NFTwallet tools 806, NFT generation tools 808, NFT collection display tools810, games 812, and database 814, etc. can likewise be incorporatedirectly into the client device 825. In this fashion, a client device825 through the application of its operating system 244 and one or moreapplications can provide a graphical user interface to operate vianetwork 115 but independently from any NFT collection platform toperform any of the functions and features described herein. Inparticular, the client device 825 can perform the functions of both theclient device and the NFT collection platform 800 without requiringcommunications to be sent to the client device 825 from a NFT collectionplatform (or NFT distribution platform) and communications sent to a NFTcollection platform (or NFT distribution platform) from the clientdevice 825.

In addition, NFT generation tools 808 can be used to protect, encryptand/or authenticate any digital information that could be stored in thewallet app 250, including for example rewards cards, coupons, movietickets, event tickets, boarding passes, public transit cards, studentID cards, credit cards, debit cards, prepaid cards, and loyalty cards.In addition, the functionality of the wallet app 250 can be furtherexpanded to protect other information such as vehicle titles, warrantycards, driver's licenses and other IDs, vaccination records,prescriptions, and/or other medical records, social security cards,financial records, authentication tokens, insurance cards, passwords,user IDs and/or other images and information of a personal and/orsensitive nature. Any of these types of digital information can beprotected via an NFT or other blockchain transaction in conjunction,with or without associated image or display data, and with or withoutmetadata and/or “other data” as that term has been used herein inassociation with the NFT generation tools 808.

FIG. 9A presents a block diagram/flow representation of an example ofNFT generation. In the example shown, an original metaverse real estateNFT 4820 corresponds to a portion/plot of real estate that is used in agame or metaverse application. An example is shown in FIG. 9B. Theoriginal metaverse real estate NFT 4820 can be purchased by the user,created or leveled-up via game play or otherwise acquired by the user ofa metaverse application or game.

The NFT generation tools 808 are used to generate a derivative NFT 4824or other metaverse real estate NFT that is based on the improvements4822 shown in FIG. 9C. In the example shown the improvements 4822correspond to a building or other structure, however, other real estateimprovements can likewise be implemented. In various example, thederivative NFT 4824 with improvements shown in FIG. 9D can be created ona parachain or other sidechain that is different from the blockchain onwhich the original metaverse real estate NFT 4820 resides or the sameblockchain on which the original metaverse real estate NFT 4820 resides.

FIG. 9E presents a flowchart representation of an example method. Inparticular, a method 4800 is presented for use in conjunction with anyof the functions and features described herein. Step 4802 includesreceiving, via the processor, a metaverse real estate NFT associatedwith metaverse real estate. Step 4804 includes receiving, via theprocessor, improvements data associated with the metaverse real estate.Step 4806 includes facilitating creation of a derivative NFT associatedwith the metaverse real estate and having improvements associated withmetaverse real estate.

FIG. 10A presents a block diagram/flow representation of an example ofNFT generation. In the example shown, document image data 4920 and otherdata corresponding to a document are used to generate an authenticateddocument NFT 4924 via the NFT generation tools 808. These authenticateddocument NFTs 4924 can be stored in an NFT wallet associated with themobile phone or other client device associated with the user and can beused, for example, in place of coupons, cards, legal documents, medicaldocuments, financial documents, IDs, credit cards, licenses and/or otherimportant documents associated with a user that normally exist innon-digital, e.g. paper or plastic form. The authenticated document NFT4924 can be used to prevent fraud and/or promote privacy in transactionsvia secure user and/or document authentication. In various examples, theauthenticated document NFT 4924 can be presented and analyzed viasecured blockchain or other crypto transactions at the time of atransaction in order to authenticate the identity of the user and/or toverify the accuracy and authentic nature of the other data 4922 and/orto facilitate the security of the transaction.

FIG. 10B presents a flowchart representation of an example method. Inparticular, a method 4900 is presented for use in conjunction with anyof the functions and features described herein. Step 4902 includesreceiving, via the processor, a document image associated with adocument. Step 4904 includes receiving, via the processor, other data,wherein the other data is also associated with the document. Step 4906includes facilitating creation of an authenticated document NFTcorresponding to the document.

FIG. 11A presents a block diagram/flow representation of an example ofNFT generation. The NFT generation tools 808 are used to generate aderivative NFT 5624 based on an original metaverse real estate NFT 5620and based on the enhancement data 5622.

In the example shown in FIG. 11B, an original metaverse real estate NFT5620 corresponds to real estate having an interior room that is used ina game or metaverse application. The original metaverse real estate NFT5620 can be purchased by the user, created or leveled-up via game playor otherwise acquired by the user of a metaverse application or game.

The NFT generation tools 808 are used to generate a derivative NFT 5624or other metaverse real estate NFT that is based on the enhancementsdata 5622 shown in FIG. 11C. In the example shown the enhancements5622-1 and 5622-2 correspond to a Moet & Chandon vending machine and aJackson Pollock painting that are acquired either as image data or asindividual NFTs. While particular enhancements are shown, other realestate enhancements can likewise be implemented including statues andother art, rugs, lamps, furniture and other furnishings and accessories,outdoor objects, appliances, knick-knacks, machinery and other virtualobjects for decorating or finishing an office, home, factory, venue orother real estate.

In the example shown in FIG. 11D, the user has placed the enhancements5622-1 and 5622-2 as desired before creating the derivative NFT 5624.The derivative NFT 5624 with improvements shown can be created on aparachain or other sidechain that is different from the blockchain onwhich the original metaverse real estate NFT 5620 resides or the sameblockchain on which the original metaverse real estate NFT 5620 resides.

FIG. 11E presents a flowchart representation of an example method. Inparticular, a method 5600 is presented for use in conjunction with anyof the functions and features described herein. Step 5602 includesreceiving, via the processor, a metaverse real estate NFT associatedwith metaverse real estate. Step 5604 includes receiving, via theprocessor, enhancement data associated with the metaverse real estate.Step 5606 includes facilitating creation of a derivative NFT associatedwith the metaverse real estate and having enhancements associated withmetaverse real estate.

FIG. 12A presents a block diagram of an example system. In particular, asystem is shown that can be implemented similarly to, or in conjunctionwith, NFT collection platform 800. The system includes an NFTtransaction authenticator 6022 and a secure real-time NFT metadatarepository 6024. In various examples, the NFT transaction authenticator6022 and the secure real-time NFT metadata repository 6024 can beimplemented via one or more modules that include a network interface,processing circuitry and memory. The secure real-time NFT metadatarepository 6024 stores NFT metadata received in conjunction with NFTscreated via metadata source 6026, such as one or more NFT creationsystems 824. The NFTs are associated with one or more users 6020.

In operation, the NFT transaction authenticator 6022 responds totransaction requests from a user associated with an NFT to authenticatethe NFT and the user and to otherwise determine the validity of thetransaction that is requested. If the user and the NFT are bothauthenticated, and the requested transaction is otherwise permissible(e.g. not restricted by conditions on use or other transactionrestrictions), then the NFT transaction authenticator 6022 responds byissuing credentials to facilitate the transaction with a third party6028. As will be discussed herein, the maintenance and use of the securereal-time NFT metadata repository 6024 allows authentication of NFTrelated transactions in real-time—avoiding possible delays inperforming, for example, complex blockchain transactions via an NFTsource 6026 where the NFT was minted and/or otherwise maintained.

Consider the following example where an NFT is created via NFT source6026. In addition to other NFT data, the NFT has metadata that uniquelyidentifies the NFT, a hash or other NFT authentication metadata that canbe used to authenticate the NFT and/or transaction restriction metadataindicating possible restrictions on transactions/use conditionsinvolving the NFT. Furthermore, when the NFT is created and/or acquiredby a user, user-specific user authentication metadata is acquired orcreated and stored on the blockchain with the NFT with the othermetadata. This user authentication metadata can include one or morepasswords, answers to security questions, identifiers of recognizeddevices such as a device identifier of a personal cellphone, laptop,tablet, computer or other known and/or trusted device, one or moretrusted networks of the user, other multifactor authentication data suchas personal information, known answers to security questions, biometricdata related to fingerprints, retinal scans, facial features or otherbiometrics of the user and/or other user authentication data that can beused to determine if a user is the owner of the NFT or otherwise anauthorized user and in particular, whether or not the user is (or isnot) who they claim to be.

The metadata associated with the NFT is indexed by NFT identifier andstored on the secure real-time NFT metadata repository 6024 for use bythe NFT transaction authenticator 6022 in authenticating NFT-relatedtransactions. This metadata is available from the repository on areal-time basis (e.g., is available with an acceptable amount of latencyassociated with a corresponding transaction). The metadata in the securereal-time NFT metadata repository 6024 is also synced periodically withthe NFT via the NFT source 6026 to reflect any changes in the NFTitself. While some metadata, such as an NFT identifier, NFTauthentication metadata and/or transaction restriction metadata may bemade accessible to the user who holds the NFT, in various examples, theuser authentication metadata in particular, can be encrypted in such afashion that is decryptable by the secure real-time NFT metadatarepository 6024—but not by the user. In various examples, the securereal-time NFT metadata repository 6024 lacks a general networkconnection and is connected to the NFT transaction authenticator 6022via a dedicated and/or otherwise secured connection or is otherwisewalled-off from other network connections of the NFT transactionauthenticator 6022. This helps prevent unauthorized tampering with thesensitive data stored therein.

When a user 6020 proposes an NFT-related transaction, the NFTtransaction authenticator 6022 collects from the user as part of thetransaction request (a) an identifier of the NFT, and NFT authenticationdata corresponding to the NFT (b) user authentication data user, and (c)information on the proposed transaction. The NFT transactionauthenticator 6022 determines whether or not the identifier correspondsto a valid NFT. If so, it retrieves the metadata associated with the NFTfrom secure real-time NFT metadata repository 6024. The NFT transactionauthenticator 6022 authenticates the NFT by comparing the NFTauthentication data to the NFT authentication metadata to determine ifthey match. The NFT transaction authenticator 6022 can also authenticatethe user 6020 to the NFT by comparing the user authentication data tothe user authentication metadata to determine if they match. Ifauthentication succeeds, the NFT transaction authenticator 6022facilitates the transaction with the third party 6028 by authorizingcompletion of the transaction, e.g. by issuing a credential to the thirdparty 6028. The credential can include any message, object, or datastructure that vouches for the identity of the user, the authenticity ofthe NFT and/or the validity of the transaction, through some method ofsecurity, trust and/or authentication.

In this fashion, the NFT transaction authenticator 6022 can authenticatetransactions such as access to a flight via a driver's license orpassport NFT, sale of a vehicle, real estate via a title NFT, a credit,debit or gift card transaction via a credit, debit or gift card NFT, thesale of a stock or bond via a stock or bond certificate NFT, warrantytransactions via a warranty card NFT, access to events via venue ticketNFTs and/or vaccination card NFTs, coupon redemption via a coupon NFT,access to a vehicle, dwelling or office via a key NFT, etc. Furthermore,the NFT transaction authenticator 6022 can authenticate transactionssuch as sales and/or micro-loans of NFTs itself.

It should be noted that some NFTs are conditional, e.g. that haverestrictions on their use and/or the transactions that are permitted.Depending on the type of transaction, the NFT transaction authenticator6022 can also operate to compare transaction data received from the userto transaction restrictions metadata to determine if a transaction ispermitted—before it is authorized. In this fashion, a credit, debit orgift card transaction can be halted if an expiration date or transactionlimit has been exceeded. A warranty transaction can be halted if thewarranty has expired. A key access for a pool, gym or office can behalted based on date, day of week or time of day restrictions, etc.

Furthermore, in sales transactions and/or micro-loans that have beenauthorized, the NFT transaction authenticator 6022 can also operate tonote the pending sale or micro-loan in the secure real-time NFT metadatarepository 6024 or otherwise place a hold on the NFT to prevent anothersales or micro-loan until the repository is updated in a future syncwith the NFT source 6026. Furthermore, in some cases the NFT correspondsto an expendable asset such as a venue ticket, gift card, coupon, etc.The NFT transaction authenticator 6022 can also operate to determinethat the NFT is expended, based on the transaction restrictions metadataand the transaction data. In response to such a determination, NFTtransaction authenticator 6022 can then update the secure real-time NFTmetadata repository to indicate the NFT is expended. In any of thesecases above, the secure real-time NFT metadata repository may facilitateupdating of the NFT source 6026 to reflect an authorized transaction vianotifications and/or that an NFT has been expended.

FIG. 12B presents a flowchart representation of an example method. Inparticular, a method 6000-4 is presented for use in conjunction with anyof the functions and features described herein. Step 6002-4 includesreceiving, at the processor, a transaction request from a userassociated with an NFT minted via a blockchain, wherein the transactionrequest includes NFT identification data identifying the NFT, NFTauthentication data, user identification data and transaction dataassociated with the transaction. Step 6004-4 includes receiving, from asecure real-time NFT metadata repository and in response to the NFTidentification data, NFT authentication metadata for authenticating theNFT, user authentication metadata for authenticating an authorized userof the NFT, and transaction restrictions data associated with the NFT,wherein the secure real-time NFT metadata repository is separate fromthe blockchain.

Step 6006-4 includes determining, via the processor, that the NFT isauthenticated when the NFT authentication data compares favorably to theNFT authentication metadata. Step 6008-4 includes determining, via theprocessor, that the user is authenticated when the user authenticationmetadata compares favorably to the user identification data. Step 6010-4includes determining, via the processor, that the transaction isauthorized when the transaction restrictions metadata compares favorablyto the transaction data. Step 6012-4 includes generating credentialsdata to facilitate the transaction when the NFT is authenticated, theuser is authenticated and the transaction is authorized.

FIG. 12C presents a pictorial block diagram/flow representation of afurther example of transaction authentication. In this case, thetransaction request 6054-1 includes NFT identification data identifyingthe NFT, NFT authentication data, and also user identification data thatincludes both a user device identifier and user biometric data that wascollected via the client device 825 as part of its own userauthentication process.

Again, the NFT transaction authenticator 6022 can in operate inconjunction with the secure real-time NFT metadata repository 6024 forexample, to authenticate the transaction with the third party 6028. Inthis additional case, the user authentication mechanisms of the clientdevice are used in the transaction of the authentication process. Oncethe user is identified by a trusted device, the device identifier of thetrusted device can be in combination with the user biometrics collectedby that device to provide further security for the proposed transaction.

FIG. 12D presents a flowchart representation of an example method. Inparticular, a method 6000-10 is presented for use in conjunction withany of the functions and features described herein. Step 6002-10includes receiving, at the processor, a transaction request from a userassociated with an NFT minted via a blockchain, wherein the transactionrequest includes NFT identification data identifying the NFT, NFTauthentication data and user identification data that includes a userdevice identifier. Step 6004-10 includes receiving, from a securereal-time NFT metadata repository and in response to the NFTidentification data, NFT authentication metadata for authenticating theNFT and user authentication metadata for authenticating an authorizeduser of the NFT, wherein the secure real-time NFT metadata repository isseparate from the blockchain.

Step 6006-10 includes determining, via the processor, that the NFT isauthenticated when the NFT authentication data compares favorably to theNFT authentication metadata. Step 6008-10 includes determining, via theprocessor, that the user is authenticated when the user authenticationmetadata compares favorably to the user identification data. Step6010-10 includes generating credentials data to facilitate thetransaction when the NFT is authenticated and the user is authenticated.

In FIG. 13A, an NFT includes (e.g. that has associated content storedon-chain or off-chain) corresponding to a playable version (e.g. a gameapplication, game binary, game data, etc.) of an electronic game (ormore simply, a “game”), such as an online game, cloud-based game, a gameapplication for a mobile device, a video game playable on a game consoleor personal computer and this is rendered on a streaming platform, inthe cloud, or locally at the client device itself. The electronic gamecan be a metaverse game or other metaverse experience, a single playergame, a multiplayer game, an action/adventure game, a real-time strategygame, a shooter game, a multiplayer online battle arena, a role-playinggame, simulation or sports game, a puzzle, party game and/or other game.

In various examples, the NFT includes (e.g. that has associated contentstored on-chain or off-chain) corresponding to a game application havingplayable game data such as graphics files, game status information,executable code or other instructions that operate in conjunction with aplatform and/or a client device to execute the play of the game itself.Furthermore, the NFT may include authentication data with respect to auser that “owns” the game NFT and this particular copy of the game andentitles the user or other holder of the NFT to play the game and othermetadata and other data as discussed herein. In the example shown, thegame NFT includes metadata that indicates that this copy corresponds toa special collector's edition of the game and, in particular, one of alimited series release of NFTs corresponding to one of the first 10,000copies of the game and/or game NFT.

While described above as a “game NFT”, such an NFT can have any of themetadata, other data, and/or operate similarly to any of the other typesof NFTs corresponding to videos, images, documents, game pieces, gamecharacters, metaverse features, and/or other objects, etc. that aredescribed herein.

FIG. 13B presents a flowchart representation of an example method. Inparticular, a method 6200-1 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-1 includesreceiving, via the processor, playable game data associated with anelectronic game to be associated with a series of NFTs. Step 6204-1includes receiving, via the processor, other data to be associated withthe series of NFTs. Step 6206-1 includes facilitating, via the processorand based on the playable game data and the other data, generation ofthe series of NFTs, each of the series of NFTs comprising a playableinstance of the electronic game.

FIG. 13C presents a pictorial representation of an example screendisplay. In the example shown, a user of an NFT game platform hasaccessed, via a client device associated with the user such as clientdevice 825, a plurality of game NFTs associated with the user. The NFTgame platform can be implemented via NFT collection platform 800, NFTdistribution platform 2800, and/or other NFT platform that can includeor operate in conjunction with NFT transaction authenticator 6022, NFTsource 6026, secure real-time NFT metadata repository 6024, NFT walletsystem 820, NFT marketplace 822, NFT creation system 824, and/or othertools, devices and systems described herein.

In this case, the user's collection of game NFTs includes NFTs 4150-1,4150-2, 4150-3, and 4150-4, etc. In various embodiments the collectiondisplay can be arranged by the user or automatically sorted intocategories such as genre's or other groupings based on metadataassociated with each of the NFTs.

In the screen display shown, the platform has generated display dataassociated with a customized collection display that contains theplurality of game NFTs for display via a graphical user interfaceassociated with the client device. Furthermore, the user has interactedwith the graphical user interface and indicated a selection of one theplurality of game NFTs for play—in this case, the game “I Dig It”. Theselection is received by the platform which responds by interacting, viathe network 115, with a client device 825 to support play of theselected game by the user—as shown in FIG. 13D. This support can includestreaming game video to, and receiving game input from, the clientdevice 625 via the network 115.

The NFT collection platform 800 and/or associated client device improvesthe technology of NFT systems and existing gaming platforms by allowingthe user to generate, store, collect, display and use game NFTs thatinclude playable content. The use of NFTs in association with playablegame content allows users to “own” playable versions of games that canbe streamed to a user's client device, to own and trade collectablelimited game edition NFTs, to loan authenticated versions of games forthe play of others, and/or to authenticate the user's ownership in thegame and the game NFT.

FIG. 13E presents a flowchart representation of an example method. Inparticular, a method 6200-2 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-2 includesaccessing, via a network interface, a plurality of game NFTs, each ofthe plurality of game NFTs associated with a game accessible by a userof a client device. Step 6204-2 includes generating, via the processor,display data associated with a customized collection display thatcontains the plurality of game NFTs for display via a graphical userinterface.

Step 6206-2 receiving, via the graphical user interface, a selection ofone the plurality of game NFTs for play of the associated game. Step6208-2 includes facilitating, via the network interface and inconjunction with the client device, play of the game associated with theone of the plurality of game NFTs.

FIG. 13F presents a block diagram/flow representation of an example ofNFT generation. In particular, game data 6226 has been collected inassociation with the user's (player's) play of a game corresponding togame NFT 6220. At some time, such as the end of a game, when a playerreaches certain goals or achievements in the game, upon expiration of apredetermined time period, upon accumulation of a predetermined amountof game play (e.g. a number of games played, an amount of play time,etc.) or other criteria, the game data 6226 is used to generate anupdate to the game NFT 6220 as the updated game NFT 6220-1. In thisfashion, the player's game play and/or performance and achievements canbe used to update the game NFT so that a player can pick up where he/sheleft off, have a mechanism to display some of theperformance/achievements in conjunction with the game NFT itself.

As used herein, the term “updated” NFT can be used to represent changesthat are made to an original NFT—i.e. the NFT that is the subject of theupdate. In addition, an “updated” NFT can be a new NFT, such as aderivative NFT, an all new NFT or other NFT that is minted based on thecontent, images, metadata and/or other data or based merely on theexistence of the original NFT. This new NFT can be minted on theoriginal blockchain used to mint the original NFT or via aparachain/side chain that is different from the original blockchain.

In FIG. 13G, an example of Game NFT 6220 corresponding to an NBA game ispresented. In FIG. 13H, game data 6226 is generated based on theplayer's play of the game and used to generate an updated game NFT6220-1. In the example shown, updated game NFT 6220-1 visually reflectsthat the player has reached the “one-star” level.

FIG. 13I presents a flowchart representation of an example method. Inparticular, a method 6200-3 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-3 includesfacilitating, via the network interface and in conjunction with theclient device, play of the game associated with the one of the pluralityof game NFTs. Step 6204-3 includes receiving, via the processor, gamedata associated with the game play of the game by a user. Step 6206-3includes updating the original NFT associated with the game piece, basedon the game data associated with the game play of the game by the user.

FIG. 13J presents a block diagram/flow representation of an example ofNFT generation. In the example shown, NFT generation tools 808 are usedto generate a derivative NFT 6224 based on the expiration restrictions6222 that is shown in FIG. 13K. The expiration restrictions cancorrespond to, for example, an expiration time and/or date, one or Ntime use in a game, tournament or challenge, etc. This derivative NFT6224 can be created on a parachain or other sidechain that is differentfrom the blockchain on which the original game NFT 6220 resides.Furthermore, this derivative NFT 6224 can be micro-loaned or otherwiseleased or loaned to another user for game play—subject to the expirationrestrictions. In this fashion, for example, other users can play thegame in exchange for a price (payment, bounty, experience, etc.).

In FIG. 13L, the derivative NFT 6224 has been temporarily loaned toanother user who plays the game. At the end of the loan (e.g. when theexpiration restrictions are met) the loaned game is automaticallydeleted, destroyed, disabled or otherwise “burned” and game data 6226indicating the end of the escrow, stats and experience or other gameperformance metrics earned by the other user via the game are retrievedand can be stored by the user on the blockchain or other decentralizedcomputer network with the original NFT 6220 to generate updated NFT6220′, as shown in FIG. 13M.

FIG. 13N presents a flowchart representation of an example method. Inparticular, a method 6200-4 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-4 includesfacilitating, via the processor, creation of a derivative NFTcorresponding to an original NFT associated with a game the derivativeNFT having expiration restrictions limiting game play of the game. Step6204-4 includes facilitating, via the processor, a micro-loantransaction of the derivative NFT to another user to facilitate the gameplay of the game by the other user, wherein the derivative NFT expireswhen the expiration restrictions are met.

FIG. 13O presents a flowchart representation of an example method. Inparticular, a method 6200-5 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-5 includesfacilitating, via the processor, creation of a derivative NFTcorresponding to an original NFT associated with a game the derivativeNFT having expiration restrictions limiting game play of the game. Step6204-5 includes facilitating, via the processor, a micro-loantransaction of the derivative NFT to another user to facilitate the gameplay of the game by the another user, wherein the derivative NFT expireswhen the expiration restrictions are met. Step 6206-5 includesreceiving, via the processor, game data associated with the game play ofthe game piece by the another user. Step 6208-5 includes updating theoriginal NFT associated with the game piece, based on the game dataassociated with the game play of the game piece by the other user.

FIG. 13P presents a flowchart representation of an example method. Inparticular, a method 6200-6 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-6 includesaccessing, via a network interface, a plurality of game NFTs, each ofthe plurality of game NFTs including a playable instance of anassociated game that is accessible by a user of a client device. Step6204-06 includes generating, via the processor, display data associatedwith a customized collection display that contains the plurality of gameNFTs. Step 6206-06 includes sending, via the network interface, thedisplay data associated with a customized collection display to theclient device for display via a graphical user interface associated withthe client device.

Step 6208-06 includes receiving, via the graphical user interface, aselection of one the plurality of game NFTs for play of the associatedgame. Step 62010-06 includes facilitating, via the network interface,play of the associated game in conjunction with the client device.

In various examples, facilitating the play of the associated gameincludes streaming, via the network interface, game video associatedwith the one of the plurality of game NFTs to the client device andreceiving from the client device, via the network interface, game dataassociated with the game play of the game by the user. The customizedcollection display that presents the plurality of game NFTs can beconfigured in response to user interactions with the graphical userinterface, configured based on metadata associated with the plurality ofgame NFTs and/for example, be configured based on genres associated withthe plurality of game NFTs or other categories or customizedarrangements, either automatically or by selection from the user.

In various examples, the method can further includes updating the gameNFT based on the game play of the associated game by the user, forexample, by minting an updated game NFT that may be minted on viaparachain that can be different from the blockchain that minted the gameNFT. The method can further include: facilitating creation of aderivative NFT corresponding to a game NFT of the plurality of gameNFTs, the derivative NFT having expiration restrictions limiting gameplay of the associated game; and facilitating a micro-loan transactionof the derivative NFT to another user to facilitate the game play of theassociated game by the another user, wherein the derivative NFT expireswhen the expiration restrictions are met. These facilitating steps canbe accomplished via NFT marketplace tools 804 and NFT generation tools808 in conjunction with, for example, one or more NFT wallet systems820, one or more NFT marketplaces 822 and one or more NFT creationsystems 824.

FIG. 13Q presents a flowchart representation of an example method. Inparticular, a method 6200-7 is presented for use in conjunction with anyof the functions and features described herein. Step 6202-7 includesreceiving, via the network interface and from a non-fungible token (NFT)game platform, display data associated with a customized collectiondisplay that presents a plurality of game NFTs, each of the plurality ofgame NFTs including a playable instance of an associated game that isaccessible by a user of the client device. Step 6204-07 includesdisplaying the display data via a graphical user interface and a displaydevice associated with the client device.

Step 6206-07 includes receiving, via the processor in response to userinteractions with the graphical user interface, a selection of one theplurality of game NFTs for play of the associated game. Step 6208-7includes sending, to the NFT game platform via the network interface,selection data indicating the selection of the one the plurality of gameNFTs. Step 6210-07 includes facilitating, via the network interface andin conjunction with NFT game platform, play of the associated game.

The NFT game platform can be implemented via NFT collection platform800, NFT distribution platform 2800, and/or other NFT platform that caninclude or operate in conjunction with NFT transaction authenticator6022, NFT source 6026, secure real-time NFT metadata repository 6024,NFT wallet system 820, NFT marketplace 822, NFT creation system 824,and/or other tools, devices and systems described herein.

In various examples, facilitating the play of the associated gameincludes receiving, via the network interface, game video associatedwith the one of the plurality of game NFTs that is streamed from the NFTgame platform and/or sending to the NFT game platform, via the networkinterface, game data associated with the game play of the game by theuser that is generated by the client device.

FIG. 14A presents a block diagram representation of an example system.The system includes a NFT platform 6500, such as NFT collection platform800, NFT distribution platform 2800 or other NFT platform that operatesto facilitate the creation of new NFTs such as game NFTs or other NFTsassociated with games or other media and/or the play of games associatedwith one or more game NFTs that have been purchased or acquired by aplayer, collector or other user. The system further includes animmutable distributed storage system 6515, a client device 825, apayment processor 6510 or other marketplace or marketplace tool, ablockchain system 6520, such as NFT creation system 824 or otherdecentralized computer system and a wallet 6526, such as NFT walletsystem 820 or other wallet.

In operation, the immutable distributed storage system 6515, such as aninterplanetary file system (IPFS) or other decentralized computersystem/network stores a game application 6518 (e.g. playable game data)such as application binary and data corresponding to an electronic game,such as a game 812 or other electronic game. This form of storagepromotes an incorruptibility and perpetual storage of the game. When aclient device generates a purchase request 6502 for a game applicationassociated with an electronic game that is received by the NFT platform6500. The NFT platform 6500 responds by generating a payment request6504 and receives a payment response 6514 indicating whether or not thepayment request is verified. In various examples, in response to thepayment response verifying the payment request, the platform system 6500facilitates the minting of a game NFT 6522 associated with theelectronic game. In addition, or in alternative, one or more game NFTscan be minted prior to sale. In this fashion, for example, a limitedand/or numbered series of game NFTs can be minted and offered for saleto collectors. Furthermore, pre-minting a number of NFTs for sale canhelp expedite the sales because the minting of the game NFTs does notneed to occur in real-time.

In various examples, minting of the game NFT 6522 includes generation ofa private key associated with the game NFT that is stored with NFTmetadata and/or other wallet data 6526 in the wallet 6526. In otherexamples, an existing private key can be retrieved and used for the samepurpose. The game NFT 6522 serves to authenticate the purchase of thegame application 6518 by the user of the client device 825 and can beused to enable play of the electronic game via the client device 825,for example, by verification of the NFT authorization via theapplication binary of the game application 6518, before the game isfully launched for game play via the client device 825. This improvesthe technology of game systems by providing a secure and incorruptiblemethodology for authenticating ownership of a game and/or authenticatingthe user to the game as the actual game owner.

While the immutable distributed storage system 6515 and the blockchainsystem 6520 are shown as separate elements, these two systems can becombined, for example, when the game NFT 6522 and the game application6518 are stored via the same blockchain. Furthermore, while the gameapplication 6518 is shown as being sent to client device 825, in otherexamples, the immutable distributed storage system 6515 and the NFTplatform 6500 can be in direct or network communication and the gameapplication 6518 can be executed by the NFT platform 6500 for game playvia the client device 825. Other configurations, combinations andconnections are likewise possible.

FIG. 14B presents a block diagram representation of an example system.In the example shown, an application execution device 6530 stores thegame application 6518 for execution having a game NFT 6522 associatedtherewith. Similar devices shown in FIG. 14A are represented by similarreference numerals. The application execution device can be a clientdevice 825, an NFT platform 800 or other NFT platform or other devicefor executing the game application 6518 to facilitate play of the game.

In operation, the application execution device 6530 operates in responseto application launch request 6532 for the game application 6518. Thisapplication launch request 6532 can be received (internally) from a userinterface associated with the application execution device 6530 (e.g. aclient device or NFT platform) and/or received from an external devicesuch as a client device, when for example, the application executiondevice 6530 corresponds to an NFT platform in communication with aclient device. Once execution of the gaming application is initiated inresponse to the application launch request 6532, launch metadata 6534 isgenerated, for example, to determine if the launch request can bevalidated. The launch metadata 6534 is sent to the wallet 6525containing a private key associated with the game NFT 6522 associatedwith a user, such as a user of the application execution device and/orthe application execution device 6530. The application execution device6530 receives from the wallet 6526, a launch response 6535 that isgenerated based on the private key. The game application generates,based on the launch response 6536, an ownership check 6536 that is sentto the blockchain system 6520 that stores the game NFT 6522. Anownership validation response 6538 is received from the blockchainsystem 6520 that enables play of the game via the game application 6518when the ownership validation response 6538 indicates ownership of thegame NFT is verified and prevents play of the game via the gameapplication 6518 when the ownership validation response 6538 indicatesownership of the game NFT is not verified. When not verified, the gameapplication 6518 can, for example, shut itself down. In this fashion,the game application 6518 can self-validate on launch to verifyownership using game NFT data in a user's wallet which holds the privatekey to the game NFT 6522.

In various examples, the launch metadata 6534 can include a current dateand time, expiration information (if any) and a version number of thegame application 6518, a counter that indicates a number of times theapplication has been executed, and/or other data corresponding to thegame NFT 6522, the game application 6518 and/or the launch. The launchresponse 6535 can include a public key associated with the game NFT6522, a signed hash that is based on the private key, the launchmetadata 6534, and/or other data/metadata to be used to validate the NFTdata from the wallet 6525 to the game NFT 6522. In this fashion, theprivate key is not shared directly with the application binary—andinstead is merely used by the wallet 6525 in a secure fashion.

The ownership check 6536 can include information from the launchresponse 6535, additional owner/user information, such as userauthentication data, associated with the user and/or owner of the gameNFT 6522 and or other and/or other data/metadata to be used to validatethe NFT data from the wallet 6525 to the game NFT 6522. In variousexamples, the blockchain system 6520 can include a an NFT transactionauthenticator 6022, a secure real-time NFT metadata repository 6024 andan NFT source 6026 that actually stores the game NFT 6522 on ablockchain or other decentralized computer system/network and userauthentication/NFT validation can take place, for example as describedin conjunction with FIGS. 12A-12D.

FIG. 14C presents a block diagram representation of an example system.This system operates similarly to the system of FIG. 14B, however, theapplication launch request 6532 is received directly from the wallet6525.

FIG. 14D presents a block diagram representation of an example system.These examples address a scenario where NFT's can be issuedin-application (in-app NFTs). These in-app NFTs can correspond tocollected or collectable items, achievements, purchased items, and orother NFTs that can be purchased or collected in-app. For example, firstlaunch for a new user can issue an unsealing/open box NFT that is thedigital equivalent of opening the box of a physical good and collectinga prize. These in-app NFT's can be tied to the user/owner of the gameNFT 6522 and/or tied to a particular instance of the game application6518. This allows some NFTs to be transferred when ownership of the gameapplication is transferred via sale or micro-loan of the game NFT 6518.In other examples, the in-app NFTs can be independently sold anddisassociated with the game NFT 6522.

In various examples, the application execution device 6530 receives anin-app issuance request 6542 from a gaming application 6518 that wasgenerated either automatically or in response to user interaction withthe game. The application execution device 6530 responds byfacilitating, based on in-app NFT data 6544, the minting of an in-gameNFT 6545 associated with the electronic game based on an authenticationof the ownership of the game application 6518 via ownership of theassociated game NFT 6522 by the user/owner that is playing the game.

In various examples, the system operates by: generating, via theapplication execution device 6530, an ownership check 6536; sending theownership check 6536 to a blockchain system 6520 that stores a game NFT6522 associated with the electronic game and the user; receiving, fromthe blockchain system 6520, an ownership validation response 6538; andfacilitating, via the game application 6518, a minting of the in-app NFT6545 when the ownership validation response 6538 indicates ownership ofthe game NFT 6518 is verified.

In this example shown, an ownership check 6536 is initiated not only onlaunch of the game application 6518, but also when an in-app issuancerequest 6542 is initiated to generate a in-app NFT. The in-app NFT 6546is only minted when a favorable ownership validation response 6538 isreceived indicating validated ownership and/or user authentication.Furthermore, a favorable payment response 6514 may be required when thein-app issuance request 6542 has an associated a cost. Otherwise, ifpayment is denied or ownership validation fails, the requested in-appNFT 6542 is not minted.

FIG. 14E presents a block diagram representation of an example system.In various examples, game application 6518 starts with a root versionthat can be designed as 6518-1. As bugs are fixed and new updates arereleased, new versions of the game application (6518-2, 8518-3 . . . )can be created

Consider the following example, where the immutable storage system 6515includes an IPFS file system. The game application 6518-1 can beuploaded and an IPFS hash of the content (a “CID,” or content address)is generated that is used to make an IPFS URL (ipfs://<cid>). This IPFSURL can be included in the NFT data of the game NFT to refer tooff-chain data (e.g., the metadata field in game NFT, the field in yourmetadata corresponding to the content—in this case the game application)as a pointer to the content itself. When there is a request to retrievethe game application 6518-1, the NFT data can be accessed from thedecentralized IPFS network from any peer that has the content. CIDsreference immutable content stored via a blockchain so that the gameapplication that is accessed is the content referenced in the game NFT.The game application 6518-1 can be fetched directly, via a public IPFSgateway, or by using an IPFS Desktop application or via an IPFS commandline.

When a new version of the game application, designated as 6518-2 isreleased, a new blockchain can be created with each block in the chainsuperseding the corresponding blocks from the previous chain. A game NFTfor the prior version of the game application 6518-1 can be used tocheck the blockchain to validate the newer version of the gameapplication 6518-2. For example, when a blockchain for a new version ofthe game application is created, its metadata can includelinks/references to one (or all) prior versions that are stored in theimmutable storage system 6515. In this fashion, an ownership checkassociated with a newer version can determine that a prior version hasbeen superseded when the newer version includes references to that priorversion. While a direct ownership check based on older NFT may initiallyfail because the corresponding older version has been superseded, theimmutable storage system 6515 can then attempt ownership checksassociated with one or more prior versions until either ownership isvalidated for one of the prior versions or there are no remaining priorversions to check.

Considering the example shown, the immutable storage system 6515 storesversions 6518-1 and 6518-2 of the game application via a blockchain orother decentralized computer network. When the game application 6518-2is launched by an application execution device 6530, an ownership check6536-1 is generated in accordance with a game NFT generated based on aprior game version of the game application 6518-1. The immutabledistributed storage system 6515 operates by determining when theownership check 6536-1 is validated to the prior game version 6518-1 andfurthermore determining when the prior game version 6518-1 has beensuperseded by the current game version 6518-2. The ownership validationresponse 6538-1 is generated to indicate ownership validation only whenboth the ownership check 6536-1 is validated to the prior game version6518-1 and when the prior game version 6518-2 has been superseded by thecurrent game version. These two steps can be performed via the oneprocess described above or via separate processes.

FIG. 14F presents a block/flow diagram representation of an examplesystem. In various examples the immutable distributed storage system6515 can also determine when updates of a game application are availableand facilitate the download of such updates.

Consider the following example. When the game application 6518-1 islaunched by an application execution device 6530, an ownership check6536-2 is generated in accordance with a game NFT generated based on the(original) game version of the game application 6518-1. The immutabledistributed storage system 6515 operates by determining when theownership check 6536-2 is validated to the game version 6518-1 andfurthermore determining when the game version 6518-1 has been supersededby the current game version 6518-2. In this case, the ownership checkcan be validated on the first instance since the launchmetadata/response data corresponds to the version of the gameapplication that is being launched. The immutable distributed storagesystem 6515 can, for example, also search the metadata, a version listassociated with the game application or other data structure, todetermine and identify another version of the game that supersedes theversion being launched. If both conditions are met, the ownershipvalidation response 6538-2 is generated to indicate that the updatedgame application 6518-2 is available. Furthermore, the immutabledistributed storage system 6515 can facilitate access, by theapplication execution device 6530, to the updated gaming application6518-2. This facilitation can be performed by coordinating with theapplication execution device 6530 to download the game application6518-2 as shown. The updated gaming application 6518-2 can then belaunched and validated as previously described in conjunction with FIG.14E.

FIG. 14G presents a flowchart representation of an example method. Inparticular, a method 6550-1 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-1 includesreceiving, at the NFT platform and from a client device, a purchaserequest for a game application associated with an electronic game. Step6554-1 includes generating a payment request in response to the purchaserequest. Step 6556-1 includes receiving a payment response verifying thepayment request. Step 6558-1 includes facilitating, in response to thepayment response verifying the payment request, via the processor, aminting of a game NFT associated with the electronic game authenticatingthe purchase of the game application.

In various examples, the application data associated with the gameapplication is stored via an immutable distributed storage system. Thegame NFT can operate to enable play of the electronic game via theclient device. Minting of the game NFT can include generation orretrieval of a private key to be associated with the game NFT and themethod can further include facilitating storage, via a wallet associatedwith a user of the client device, of the private key associated with thegame NFT.

FIG. 14H presents a flowchart representation of an example method. Inparticular, a method 6550-2 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-2 includesreceiving, from a client device, an application launch request for agame application having a game NFT associated therewith. Step 6554-2includes generating, via the game application and in response to theapplication launch request, launch metadata. Step 6556-2 includessending the launch metadata to a wallet associated with a user of theclient device, the wallet containing a private key associated with thegame NFT.

Step 6558-2 includes receiving, from the wallet, a launch response thatis generated based on the private key. Step 6560-2 includes generating,via the game application and based on the launch response, an ownershipcheck. Step 6562-2 includes sending the ownership check to a blockchainsystem that stores the game NFT. Step 6564-2 includes receiving, fromthe blockchain system, an ownership validation response. Step 6566-2includes enabling, via the game application, play of the game when theownership validation response indicates ownership of the game NFT isverified. Step 6568-2 includes preventing, via the game application,play of the game when the ownership validation response indicates theownership of the game NFT is not verified.

In various examples, the application data associated with the gameapplication is stored via an immutable distributed storage system. Thegame NFT can enable play of the electronic game via the client device.The game NFT can include generation of a private key associated with thegame NFT and the method can further include facilitating storage, via awallet associated with a user of the client device, of the private keyassociated with the game NFT.

FIG. 14I presents a flowchart representation of an example method. Inparticular, a method 6550-3 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-3 includesreceiving, at the client device, an application launch request for agame application having a game NFT associated therewith. Step 6554-3includes generating, via the game application and in response to theapplication launch request, launch metadata. Step 6556-3 includessending the launch metadata to a wallet associated with a user of theclient device, the wallet containing a private key associated with thegame NFT. Step 6558-3 includes receiving, from the wallet, a launchresponse that is generated based on the private key.

Step 6560-3 includes generating, via the game application and based onthe launch response, an ownership check. Step 6562-3 includes sendingthe ownership check to a blockchain system that stores the game NFT.Step 6564-3 includes receiving, from the blockchain system, an ownershipvalidation response. Step 6566-3 includes enabling, via the gameapplication, play of the game when the ownership validation responseindicates ownership of the game NFT is verified. Step 6568-3 includespreventing, via the game application, play of the game when theownership validation response indicates the ownership of the game NFT isnot verified.

FIG. 14J presents a flowchart representation of an example method. Inparticular, a method 6550-4 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-4 includesreceiving, at the NFT wallet associated with a user of a client device,an application launch request for a game application having a game NFTassociated therewith, wherein the NFT wallet contains a private keyassociated with the game NFT. Step 6554-4 includes generating, via theNFT wallet and in response to the application launch request, a launchresponse that is generated based on the private key, wherein the gameapplication generates, based on the launch response, an ownership checkthat is sent to a blockchain system that stores the game NFT, andwherein the game application receives, from the blockchain system, anownership validation response and enables play of the game when theownership validation response indicates ownership of the game NFT isverified and prevents play of the game when the ownership validationresponse indicates the ownership of the game NFT is not verified.

FIG. 14K presents a flowchart representation of an example method. Inparticular, a method 6550-5 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-5 includesreceiving, at the NFT platform and from a game application associatedwith an electronic game played by a user, an in-app issuance request foran in-app NFT. Step 6554-5 includes generating, via the NFT platform, anownership check. Step 6556-5 includes sending the ownership check to ablockchain system that stores a game NFT associated with the electronicgame and the user. Step 6558-5 includes receiving, from the blockchainsystem, an ownership validation response. Step 6560-5 includesfacilitating, via the game application, a minting of the in-app NFT whenthe ownership validation response indicates ownership of the game NFT isverified.

In various examples, the method further includes: generating a paymentrequest in response to the purchase request; and receiving a paymentresponse verifying the payment request; wherein the ownership check isgenerated in response to the payment response. The in-app NFT can havein-app NFT metadata associated therewith, wherein the in-app NFTmetadata includes one or more of: an achievement data associated withthe electronic game and the user, an application identifier associatedwith the electronic game, a user identifier associated with the user oran instance identifier indicating an instance of the electronic gameassociated with the user.

FIG. 14L presents a flowchart representation of an example method. Inparticular, a method 6550-6 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-6 includesreceiving, at the blockchain system and from a game applicationassociated with an electronic game, an ownership check generated inaccordance with a game non-fungible token (NFT), wherein the gameapplication is associated with a current game version of the gameapplication and the game NFT was generated based on a prior game versionof the game application. Step 6554-6 includes determining, via theblockchain system, when the ownership check is validated to the priorgame version. Step 6556-6 includes determining, via the blockchainsystem, when the prior game version has been superseded by the currentgame version. Step 6558-6 includes generating an ownership validationresponse indicating ownership validation when the ownership check isvalidated to the prior game version and when the prior game version hasbeen superseded by the current game version.

FIG. 14M presents a flowchart representation of an example method. Inparticular, a method 6550-7 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-7 includesreceiving, from a client device, an application launch request for agame application having a game NFT associated therewith. Step 6554-7includes generating, via the game application and in response to theapplication launch request, launch metadata. Step 6556-7 includessending the launch metadata to a wallet associated with a user of theclient device, the wallet containing a private key associated with thegame NFT. Step 6558-7 includes receiving, from the wallet, a launchresponse that is generated based on the private key. Step 6560-7includes generating, via the game application and based on the launchresponse, an ownership check.

Step 6562-7 includes sending the ownership check to a blockchain systemthat stores the game NFT. Step 6564-7 includes receiving, from theblockchain system, an ownership validation response that indicates anupdated game application is available. Step 6566-7 includes facilitatingaccess, by the client device, to the updated gaming application.

FIG. 14N presents a flowchart representation of an example method. Inparticular, a method 6550-8 is presented for use in conjunction with anyof the functions and features described herein. Step 6552-8 includesreceiving an application launch request for a game application having agame non-fungible token (NFT) associated therewith. Step 6554-8 includesgenerating, via the game application and in response to the applicationlaunch request, launch metadata. Step 6556-8 includes sending the launchmetadata to an NFT wallet, the NFT wallet containing a private keyassociated with the game NFT. Step 6568-8 includes receiving, from theNFT wallet, a launch response that is generated based on the privatekey.

Step 6560-8 includes generating, via the game application and based onthe launch response, an ownership check. Step 6562-8 includes sendingthe ownership check to a blockchain system that stores the game NFT.Step 6564-8 includes receiving, from the blockchain system, an ownershipvalidation response. Step 6566-8 includes enabling, via the gameapplication, play of the game when the ownership validation responseindicates ownership of the game NFT is verified.

In various examples, the method includes preventing, via the gameapplication, play of the game when the ownership validation responseindicates the ownership of the game NFT is not verified. The applicationdata associated with the game application can be stored via an immutabledistributed storage system and be downloaded to a client device or NFTplatform for execution of the game application. The application launchrequest can be generated by a client device, and wherein the gameapplication is executed via the client device or via an NFT platform incommunication with the client device.

In various examples, the ownership validation response indicates when anupdated game application is available and the method further includes:facilitating access to the updated gaming application when the updatedgame application is available. The application launch request can begenerated by a client device, wherein the gaming application is executedby the client device, and wherein facilitating access to the updatedgaming application includes downloading the updated gaming applicationto the client device for execution via the client device. Theapplication launch request can be generated by a client device, whereinthe gaming application is executed by an NFT platform in communicationwith the client device, and wherein facilitating access to the updatedgaming application includes downloading the updated gaming applicationto the NFT platform for execution via the NFT platform.

While the forgoing systems and methods of FIGS. 14A-14N have focused ongame NFTs, these systems and methods could likewise be applied to NFTsassociated with other applications, other media and/or other types ofNFTs. Furthermore, the applications and techniques associated with NFTspreviously described in this application, and in copending U.S.application Ser. No. 17/656,084 entitled, FACILITATING PLAY OF GAME NFTSVIA A CLIENT DEVICE, can likewise be applied to game NFTs as well.

FIG. 15A presents a block diagram representation of an example system.In the example shown, a user of an NFT game platform 6625 has accessed,via a client device associated with the user such as client device 825,a multiplayer game playable by the user in conjunction with users ofother client devices 825. The NFT game platform can be implemented viaNFT game platform 6500, NFT collection platform 800, NFT distributionplatform 2800, and/or other NFT platform that can include or operate inconjunction with NFT transaction authenticator 6022, NFT source 6026,secure real-time NFT metadata repository 6024, NFT wallet system 820,NFT marketplace 822, NFT creation system 824, and/or other tools,devices and systems described herein.

The NFT game platform 6625 and/or associated client device 825 improvesthe technology of NFT systems and existing gaming platforms by allowingthe user to generate, store, collect, display and use NFTs that enablegame play of the associated multiplayer games. These NFTs may be gameNFTs as previously discussed that allow a user to access gameapplications that are stored via blockchain or other immutable storagevia the game NFT. These NFTs may also be “game token” NFTs that, whilenot associated with storage and/or authentication of the gameapplication itself, nevertheless are associated with a user's ownershipof and/or access to a particular game and can be used by a gameapplication, client device 825 and/or game platform 6625 to provideauthenticated access by the user to a game that, for example can beexecuted and/or streamed to a user's client device. Like the game NFT'spreviously discussed, the game token NFTs can be collected, traded, soldor loaned for play of the game by others.

FIGS. 15B-15J present pictorial representations of example screendisplays. In FIG. 15B, the user's collection of game token NFTs includesNFTs 6650-1, 6650-2, 6650-3, and 6650-4, etc. In various embodiments thecollection display can be arranged by the user or automatically sortedinto categories such as genre's or other groupings based on metadataassociated with each of the NFTs.

In the example shown, the platform has generated display data associatedwith a customized collection display that contains the plurality of gametoken NFTs for display via a graphical user interface associated withthe client device. Furthermore, the user has interacted with thegraphical user interface and indicated a selection of one the pluralityof game token NFTs for play—in this case, the game “I Dig It”. Theselection is received by the platform which responds by interacting, viathe network 115, with a client device 825 to authenticate the user'saccess to the game via validation of the game token NFT as shown in FIG.15C. In this fashion, the play of the selected game can be enabled forthe user and/or other user's also having their own valid game token NFTscorresponding to the game as shown in FIG. 15D. Conversely, a userattempting to play without an associated game token NFT can be preventedaccess to the game.

NFT game platform 6625 can support other use of NFTs in conjunction withgames, such as multiplayer games. Consider a multiplayer game thatallows players to mine for or otherwise collect NFTs that are dropped inthe game at various times, included in game levels, dropped in the gamefor tournaments and/or otherwise placed in a game to be issued to thefirst player that is able to find or otherwise earn the NFT. In variousexamples, the types of NFTs that are collected can fall within threedifferent categories that are described below.

Non-Utilitarian Game NFT

This is a game-related NFT (that is specific to the game) that iscollected or earned via game play of a game and that provides no benefit(direct or indirect) to the player in the game—but rather may derivevalue as a as a symbol of the player's prowess and/or as collector'sitem that may be bartered or sold apart from the game. An example is awinner's trophy or badge NFT that represents an accomplishment but thatdoes not provide any tangible benefit in terms of player abilities, tothe player (or the player's character) within the game itself—otherthan, optionally, as a symbol of the player's status. A further exampleis a NFT associated with a sponsor that may or may not providesubsidiary benefits with respect to a sponsor's products and/orservices—but no benefits to the user's play of the game.

Direct-Beneficial Game NFT

This is a game-related NFT (that is specific to the game) that ispurchased, collected or earned via game play of a game and that providesa direct benefit to the player in the game by enabling and/orautomatically providing player access to player abilities, advantages,enhanced skills, unlocking additional features, and/or automaticallyproviding player access to other enhancements to the player's characterthat are nonfungible, unique or of a limited nature, and associated withthe NFT. Examples include an NFT associated with a unique or one of alimited set of weapons, armor or other game artifacts, a unique plot ofmetaverse game real estate, access to a new and/or hidden level of thegame, a player token associated with the player's character or newcharacter to be used by the player or other direct benefit to the playeror player's character within the game.

Indirect-Beneficial Game NFT This is a game-related NFT that ispurchased, collected or earned via game play of a game and that providesan indirect benefit to the player in the game, by providing one or moretokens, points or game currency that are fungible and not unique to theNFT (i.e could be gathered or earned in different ways), but which aplayer may choose to convert to direct benefits such as advantages,enhanced skills, unlocking additional features, and/or access to otherenhancements to the player's character. Examples include a game tokenthat allows a player to play again, an NFT which entitles a player tocertain benefits only after other NFTs have been collected (i.e. havinga contingent benefit), a level-up benefit which could be achieved inother ways, and/or points or game currency that can be achieved in otherways and that can be converted, at the player's discretion, into adirect benefit to the player or player's character within the game.

Consider the screen shown in FIG. 15E of a multiplayer I Dig It game.The player's character is a digger that is digging/mining to collect digup stuff (“diggins”) that can be collected by the player that firstfinds them and sold in the game in exchange for game currency that canbe used to fuel and/or upgrade the player's digger. One or more of thesediggins can be NFTs including one or more Non-Utilitarian Game NFTs, oneor more Direct-Beneficial Game NFTs and/or one or moreIndirect-Beneficial Game NFTs.

In various examples, either during regular game play or during a limitedtime tournaments, multiplayer games are populated with players in groupsof N (say 6, 10, 25, 100, etc.), so that the number of competitors arelimited and the processing resources required for each game can becapped to a maximum level. In this fashion, multiple games/tournamentscan be formed serially and/or contemporaneously as each newgame/tournament is filled until a maximum number of games/tournaments isreached. This improves the technology of multiplayer gaming by allowingprocessing resources to be predicted and allocated more efficiently tosupport multiple games.

For each game/tournament, a fixed number of NFTs are created andvirtually buried in the I Dig It world for each tournament (X NFTs pertournament). These NFTs could be, for example, one or moreNon-Utilitarian Game NFTs, one or more Direct-Beneficial Game NFTsand/or one or more Indirect-Beneficial Game NFTs that are each eitheroriginal NFTs or derivative NFTs in a limited series. The players canplay normally and look for resources and regular prizes but also couldfind an NFT. The first to find an NFT can collect the NFT (agame-collected NFT) which is then issued to the player. The game displaycan include a score board of player scores that also indicates NFTsfound—how many are left etc. Players not finding NFTs can accessinformation indicating others who won NFTs and where they were found inthe virtual world.

In various examples, the game platform 6625 further operates viaindividual instances of the game application being executed for eachplayer that operate independently in most circumstances with only alimit the number of server interactions that are each triggered byspecial circumstances within the game. This allows the game platform6625 to support more players in each game/tournament and/or morecontemporaneous games/tournaments with fewer processing resources. Invarious examples, each game application includes a player dashboard thatincludes game clock that presents a display of time left in theparticular game/tournament that is synchronized when a player starts thegame/tournament. To collect NFTs and/or to add to their score, playersmust enter and drop off their loot/diggins at a particular check-inlocation in the game (i.e., a verification site). This triggers a serverinteraction which updates the player's score. During this exchange, theplayer can view a tournament scoreboard that includes scores for otherplayers that have only been updated from the last time each playervisited the check-in location.

In various examples, NFTs that were collected by a player can only beofficially earned (and issued to the player) if the player is the firstto show up with the NFT at the check-in location in the game. Considerthe following example process:

-   -   A player collects an NFT and the game checks to see if it has        already been cashed in/earned by another player;    -   If not yet collected—the player can pick it up and game provides        a warning that the player must successful exit and cash it in at        the check-in location in order to earn it.    -   Once the player arrives at the check-in location with the NFT,        the game checks again to see if it previously was cashed in by a        previous player. If not, it is awarded (issued) to the player.        If so, the player is not awarded the NFT.

In FIG. 15F, a player has collected an example of an Indirect-BeneficialNFT that by itself does not provide additional player abilities, but canbe collected at the check-in location (if the player was the first tocheck-in with this particular NFT). If the NFT was successfullycollected (or in other examples, whether the NFT was earned or not), theplayer also receives a certain amount of game currency that itself canbe used as a basis of game score for the player, and/or further can beexchanged to enhance the player's abilities.

In FIG. 15G, a player has collected an example of a Direct-BeneficialNFT that if successfully collected, not only includes the NFT, but alsoprovides a special enhanced digger to the player. In FIG. 15H, theplayer's character is approaching a check-in location 6643 in the game.In FIG. 15I, a player has earned an example of a Non-Utilitarian NFT,for winning a particular tournament. This particular Non-Utilitarian NFTcan automatically be earned by winning the associated game/tournamentwithout the collection process through the check-in location. In otherexamples however, other Non-Utilitarian NFTs could be earned through thecollection process previously described.

While the prior examples have been focused on the collection of NFTs,similar procedures can be used to earn crypto-currency that has beendropped in a game for possible player collection. In FIG. 15J. a playerhas collected an Amp Coin.

In various examples, the game platform 6625 can support three differentcurrencies:

-   -   A game currency that can only be used in-game, e.g. a        game-dependent currency (e.g. game dollars, coins, etc.) that        only exists in (or is only relevant to) the game and can be used        to purchase resources used in the game. Game currency is earned        based on achievements associated with game play either in        tournaments and/or regular game play.    -   A non-game standard (non-crypto) currency—a game-independent        currency that exists outside of the game, can also be used to        purchase resources used in the game (including the game currency        via in-app purchases), but can also be bought/sold by others        without relation to the game (e.g. the US dollar).    -   A non-game crypto-currency, a crypto currency, e.g. a        game-independent crypto-currency (e.g. Amp coins, Bit coins,        Doge coins, etc.) that exists outside of the game, may or may        not be used to purchase resources used in the game, but can be        bought/sold by others without relation to the game.    -   A game crypto-currency, a crypto currency, e.g. a game-based        crypto-currency that is unique to the game, and may be used to        purchase resources used in the game, but also can be bought/sold        by others without relation to the game as collectables or use by        other players in the game.

In various example, non-game crypto-currency can be earned in differentways:

-   -   Non-game crypto-currency can be earned based on locating        crypto-currency coins during games/tournaments. The first player        to successfully collect a coin, earns the coins.    -   Non-game crypto-currency can also be earned based on        game/tournament results. In various examples, amounts of        crypto-currency can be awarded to first place, second place,        third place, etc. In addition or in the alternative, at the end        of the tournament, the first place player takes a percentage of        any undiscovered crypto-currency coins (in addition to whatever        they found themselves). The second place player takes a lower        percentage of undiscovered crypto-currency coins (in addition to        whatever they found themselves), etc.        It should be noted that game crypto-currency can be earned in        any of the ways described above with respect to non-game        crypto-currency.

FIG. 15K presents a block/flow diagram representation of an examplesystem of an example of NFT generation. In the example shown, NFTgeneration tools 808 operate to convert image data 6620-1 and other data6622-1 into one or more non-utilitarian NFTs 6624-1. The image data6620-1 can correspond to an original NFT, borrowed (e.g. temporarymicro-loaned) NFT, a derivative NFT, an original image, and/or otherderivatives or micro-loans thereof or other display or image data. Invarious examples, the NFT generation tools 808 can operate to verify thecredentials of any NFTs whose images are contained in the image data6620-1, prior to creating the non-utilitarian NFT 6624-1. In thisfashion, one or more non-utilitarian NFT 6624-1 can only be created(e.g. on a derivative basis) when the source NFT or NFTs areverified—preventing the creation of unauthorized or counterfeit NFTs.

The other data 6622-1, can be image data including signatures and otherendorsement images, visual indications of derivative series, originalityclassification, attributions, or other image data, metadata of all kindsincluding metadata indicating one or more originality classifications,attributions, endorsement data, other derivative data indicating theseries number and total number in a derivative series, restrictions onmicro-loans or other derivatives, restrictions on derivatives withartistic effects, restrictions that derivatives must includeattributions to the original source, restrictions on numbers ofderivatives or micro-loans or the sizes of derivative series,restrictions on the creation of collection NFTs, the number ofcollection NFTs, the creation of collection NFTs including NFTs fromother sources, from prohibited sources or with prohibited content,geographical restrictions, time restrictions (e.g., can be used tocreate derivatives or collection NFTs or can be temporarily micro-loanedfor 1 month, one year, etc., other restrictions and/or other dataassociated with, or to be associated with, the image data 6620-1.

This other data 6622-1 can be used to generate an NFT and/or combinedwith the image data 6620-1 to create a dataset that includes both theimage data 6620-1 and the other data 6622-1. This other data 6622-1 orcombined dataset can be protected via the blockchain decentralizedcomputer network and/or other crypto-based NFT creation technology thatis employed by the NFT generation tools 808 and via the NFT creationsystem 824 to create and protect the new non-utilitarian NFT 6624-1itself. It should be noted that the non-utilitarian NFT 6624-1 caninclude a single derivative or a number of derivatives, including alimited series of derivatives. It should be noted further that some orall of the other data 6622-1, including restriction data and/orattribution data, can be derived from one or more original NFTs whoseimages are associated with the image data 6620-1.

FIG. 15L presents a flowchart representation 6600-1 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6602-1 includesreceiving, via the processor, an image to be associated with a series ofnon-utilitarian NFTs corresponding to a multiplayer game. Step 6604-1includes receiving, via the processor, other data, wherein the otherdata is also associated with the series of non-utilitarian NFTs. Step6604-1 includes facilitating creation of the series of non-utilitarianNFTs.

FIG. 15M presents a block/flow diagram representation of an examplesystem of an example of NFT generation. In the example shown, NFTgeneration tools 808 operate to convert image data 6620-2 and other data6622-2 into a series of derivative NFTs 6624-2. The image data 6620-2can correspond to an original NFT, borrowed (e.g. temporarymicro-loaned) NFT, a derivative NFT, an original image, and/or otherderivatives or micro-loans thereof or other display or image data. Invarious examples, the NFT generation tools 808 can operate to verify thecredentials of any NFTs whose images are contained in the image data6620-2, prior to creating the non-utilitarian NFT 6624-2. In thisfashion, one or more non-utilitarian NFT 6624-2 can only be created(e.g. on a derivative basis) when the source NFT or NFTs areverified—preventing the creation of unauthorized or counterfeit NFTs.

The other data 6622-2 can be any of the other data 6622-1. This otherdata 6622-2 an image data 6620-2 can be protected via the blockchainand/or other crypto-based NFT creation technology that is employed bythe NFT generation tools 808 and via the NFT creation system 824 tocreate and protect the series of derivative NFTs 6624-2. It should benoted that the series of derivative NFTs 6624-2 can include a number ofderivatives, including a limited series of derivatives. It should benoted further that some or all of the other data 6622-2, includingrestriction data and/or attribution data, can be derived from one ormore original NFTs whose images are associated with the image data6620-2.

FIG. 15N presents a flowchart representation 6600-2 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6602-2 includesreceiving, via the processor, an image to be associated with a series ofderivative NFTs corresponding to a multiplayer tournament. Step 6604-2includes receiving, via the processor, other data, wherein the otherdata is also associated with the series of derivative NFTs. Step 6602-2includes facilitating creation of the series of derivative NFTs.

FIG. 15O presents a flowchart representation 6600-3 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6602-3 includesaccessing, via a network interface, a plurality of game token NFTs, eachof the plurality of game token NFTs associated with a multiplayer gameaccessible by a user of a client device. Step 6604-3 includesgenerating, via the processor, display data associated that theplurality of game token NFTs for display via a graphical user interfaceof the client device. Step 6606-3 includes receiving, via the graphicaluser interface, a selection of one the plurality of game token NFTs forplay of the associated multiplayer game. Step 6608-3 includesfacilitating, via the network interface and in conjunction with theclient device, play of the multiplayer game associated with the one ofthe plurality of game NFTs, when the one of the plurality of game tokenNFTs is selected.

FIG. 15P presents a flowchart representation 6600-4 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6602-4 includesfacilitating, via a network interface and in conjunction with a clientdevice, play of a multiplayer game by a player of a plurality ofplayers, wherein the player is associated with the client device. Step6604-4 includes updating, via the processor, the multiplayer game toreflect that the player has collected an NFT from the multiplayer gamewhen the player is determined to be a first player of a plurality ofplayers to deposit the NFT at a collection verification site in themultiplayer game. Step 6606-4 includes issuing the NFT from themultiplayer game to the player when the player is determined to be thefirst player of a plurality of players to deposit the NFT at acollection verification site in the multiplayer game.

FIG. 15Q presents a flowchart representation 6600-5 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6602-5 includesfacilitating, via a network interface and in conjunction with a clientdevice, play of a multiplayer game by a player of a plurality ofplayers, wherein the player is associated with the client device. Step6604-5 includes updating, via the processor, the multiplayer game toreflect that the player has collected crypto-currency from themultiplayer game when the player is determined to be a first player of aplurality of players to deposit the crypto-currency at a collectionverification site in the multiplayer game. Step 6606-5 includes issuingthe crypto-currency from the multiplayer game to the player when theplayer is determined to be the first player of a plurality of players todeposit the crypto-currency at a collection verification site in themultiplayer game.

FIG. 15R presents a flowchart representation 6600-6 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6602-6 includesfacilitating, via a network interface and in conjunction with a clientdevice, play of a multiplayer game by a player of a plurality ofplayers, wherein the player is associated with the client device. Step6604-6 includes updating, via the processor, the multiplayer game toreflect that the player has collected crypto-currency from themultiplayer game. Step 6606-6 includes updating, via the processor, themultiplayer game to reflect that the player has collected gamedependent-game currency from the multiplayer game. Step 6608-6 includesupdating, via the processor, the multiplayer game to reflect that theplayer has purchased game dependent currency for the multiplayer gamevia game independent currency that differs form the crypto-currency.Step 6610-6 includes updating, via the processor, the multiplayer gameto reflect that the player has purchased game dependent currency for themultiplayer game via the crypto-currency.

FIG. 16A presents a block diagram representation of an example system.In the system shown, a game token NFT 6722 is purchased and issued to aparticular user of a client device 825. The game token NFT 6722, aspreviously discussed, while not associated with storage of the gameapplication, nevertheless are associated with a user's ownership ofand/or access to a particular game and can be used by a gameapplication, client device 825 and/or game platform 6625 to provideauthenticated access by the user to a game that, for example can beexecuted and/or streamed to a user's client device in order for the userto play the game.

The system includes a NFT platform 6725, such as NFT collection platform800, NFT game platform 6500, NFT distribution platform 2800 or other NFTplatform that operates to facilitate the creation of new NFTs such asgame NFTs or other NFTs associated with games or other media and/or theplay of games associated with one or more game NFTs that have beenpurchased or acquired by a player, collector or other user. The systemfurther includes a client device 825, a payment processor 6710 or othermarketplace or marketplace tool, a blockchain system 6720, such as NFTcreation system 824 or other decentralized computer network and a wallet6726, such as NFT wallet system 820 or other wallet.

A client device generates a purchase request 6702 for a game token NFT6722 associated with an electronic game that is received by the NFT gameplatform 6725. The NFT game platform 6725 responds by generating apayment request 6704 and receives a payment response 6714 indicatingwhether or not the payment request is verified. In various examples, inresponse to the payment response verifying the payment request, the NFTgame platform system 6725 facilitates the minting of a game token NFT6722 associated with the electronic game. In addition, or inalternative, one or more game token NFTs can be minted prior to sale. Inthis fashion, for example, a limited and/or numbered series of gametoken NFTs can be minted and offered for sale to collectors.Furthermore, pre-minting a number of NFTs for sale can help expedite thesales because the minting of the game token NFTs does not need to occurin real-time.

In various examples, minting of the game token NFT 6722 includesgeneration of a private key associated with the game token NFT that isstored with NFT metadata and/or other wallet data 6726 in the wallet6726. In other examples, an existing private key can be retrieved andused for the same purpose. The game token NFT 6722 serves toauthenticate the purchase of the game or access to a game/tournament orgame application by the user of the client device 825 and can be used toenable play of the electronic game via the client device 825, forexample, by verification of the NFT authorization before the game isfully launched for game play via the client device 825. This improvesthe technology of game systems by providing a secure and incorruptiblemethodology for authenticating game/tournament access and/orauthenticating the user to the game as the actual game owner or otherauthorized user/player. While a particular architecture is shown, otherconfigurations, combinations and connections are likewise possible.Furthermore, other authentication systems & methodologies describedherein, including any of the techniques described in conjunction withFIGS. 12A-12D, could likewise be employed.

FIG. 16B presents a flowchart representation 6700-1 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6702-1 includesreceiving, at the NFT platform and from a client device, a purchaserequest for a game token NFT associated with an electronic game. Step6704-1 includes generating a payment request in response to the purchaserequest. Step 6706-1 includes receiving a payment response verifying thepayment request. Step 6708-1 includes facilitating, in response to thepayment response verifying the payment request, via the processor,issuance of a game token NFT associated with the electronic game forenabling play of the electronic game.

FIG. 16C presents a block/flow diagram representation of an examplesystem. In this example, ownership (e.g. authenticated ownership) by auser of one or more non-game NFTs 6721-2 is used to automaticallytrigger the generation of a game token NFT 6724-2 based on other data6722-2. As used herein, a non-game NFT is an NFT that, even though itmay provide benefits to a particular game and have value to collectorsindependent of a particular, it is not specific to a particular game. Inthis fashion, a game studio may issue NFTs that provide subsidiarybenefits to a number of different games as opposed to one specific game.For example, one or more non-game NFTs 6721-2 associated with InMotionGames, may provide benefits to a number of different games produced byInMotion, as opposed to any one specific game.

In the example shown in FIG. 16D, after a non-game NFTs 6721-2associated with InMotion Games is authenticated to the user, game tokenNFTs 6724-2 are generated as a result. While ownership/collection of asingle NFT triggers generation of multiple game token NFTs, in otherexamples, ownership collection of multiple non-game NFTs may be requiredto generate either a single game token NFT or a series of game tokenNFTs associated with a single game or different games.

In this fashion, a non-game NFT associated with a film or series offilms, may provide benefits to a particular game that is based oncharacters from the film(s), even though it is primarily associated withthe film(s) themselves. For example, a non-game NFT associated withHarry Potter series of films may provide subsidiary benefits to aparticular game that is based on characters from the Harry Potterfilm(s), even though the NFT is primarily associated with the film(s)themselves. In this fashion, a non-game NFT associated with an unrelatedproduct, may provide subsidiary benefits to a particular game that issponsored by the producer of this product. For example, a Fritos NFT mayprovide benefits to a particular game that is sponsored by Frito-Lay.

In this context, the other data 6722-2 can include the particular imageto be associated with the game token NFT 6724-2 along with other dataused in NFT generation as previously described herein.

FIG. 16E presents a flowchart representation 6700-2 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6702-2 includesdetermining, via the processor, when one or more non-game NFTs areauthenticated. Step 6704-2 includes receiving, via the processor, otherdata, wherein the other data is associated with a game token NFT to begenerated. Step 6706-2 includes facilitating creation of the game tokenNFT based on the other data, when the one or more non-game NFTsassociated with the multiplayer game are authenticated.

FIG. 16F presents a block/flow diagram representation of an examplesystem. In this example, ownership (e.g. authenticated ownership) by auser of one or more game-collected NFTs 6721-3 is used to automaticallytrigger the generation of a game token NFT 6724-3 based on other data6722-3. As used herein, a game collected NFT is an NFT that wascollected via play/use of a game to be associated with the game token.In the example shown in FIG. 16G, after a user/player has collected NFTs6721-3 via play of I Dig It, and these NFTs are authenticated to theuser, game token NFT 6724-2 is generated as a result. In this fashion, auser can collect new game tokens to a game that can be used in futureplay if older game tokens to that game expire after a time or due to theloss of the game by a player. These new game tokens can also be barteredor sold.

FIG. 16H presents a flowchart representation 6700-3 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6702-3 includesdetermining, via the processor, when one or more game-collected NFTsassociated with a multiplayer game are authenticated. Step 6704-3includes receiving, via the processor, other data, wherein the otherdata is associated with a game token NFT to be generated. Step 6706-3includes facilitating creation (e.g., issuance) of the game token NFTbased on the other data, when the one or more game-collected NFTsassociated with the multiplayer game are authenticated.

FIGS. 16I-16J present a block/flow diagram representations of examplesystems. In the example shown in FIG. 16I, an application executiondevice 6730 stores the game application 6718 for execution having a gametoken NFT 6722 associated therewith. Similar devices shown in FIG. 16Aare represented by similar reference numerals. The application executiondevice can be a client device 825, an NFT platform 800, NFT gameplatform 6625, NFT game platform 6500 or other NFT platform or otherdevice for executing the game application 6718 to facilitate play of thegame.

In operation, the application execution device 6730 operates in responseto an application launch request 6732 for the game application 6718.This application launch request 6732 can be received (internally) from auser interface associated with the application execution device 6730(e.g. a client device or NFT platform) and/or received from an externaldevice such as a client device, when for example, the applicationexecution device 6730 corresponds to an NFT platform in communicationwith a client device. Once execution of the gaming application isinitiated in response to the application launch request 6732, launchmetadata 6734 is generated, for example, to determine if the launchrequest can be validated. The launch metadata 6734 is sent to the wallet6725 containing a private key associated with the game token NFT 6722associated with a user, such as a user of the application executiondevice and/or the application execution device 6730. The applicationexecution device 6730 receives from the wallet 6726, a launch response6735 that is generated based on the private key. The game applicationgenerates, based on the launch response 6736, an ownership check 6736that is sent to the blockchain system 6720 that stores the game tokenNFT 6722. An ownership validation response 6738 is received from theblockchain system 6720 that enables play of the game via the gameapplication 6718 when the ownership validation response 6738 indicatesownership of the game token NFT 6722 is verified and prevents play ofthe game via the game application 6718 when the ownership validationresponse 6738 indicates ownership of the game token NFT 6722 is notverified. When not verified, the game application 6718 can, for example,shut itself down. In this fashion, the game application 6718 canself-validate on launch to verify ownership/authorized use by the userusing game token NFT data in a user's wallet which holds the private keyto the game token NFT 6722.

In various examples, the launch metadata 6734 can include a current dateand time, expiration information (if any) and a version number of thegame application 6718, a counter that indicates a number of times theapplication has been executed, and/or other data corresponding to thegame token NFT 6722, the game application 6718 and/or the launch. Thelaunch response 6735 can include a public key associated with the gametoken NFT 6722, a signed hash that is based on the private key, thelaunch metadata 6734, and/or other data/metadata to be used to validatethe NFT data from the wallet 6725 to the game token NFT 6722. In thisfashion, the private key is not shared directly with the applicationbinary—and instead is merely used by the wallet 6725 in a securefashion.

The ownership check 6736 can include information from the launchresponse 6735, additional owner/user information, such as userauthentication data, associated with the user and/or owner of the gametoken NFT 6722 and or other and/or other data/metadata to be used tovalidate the NFT data from the wallet 6725 to the game token NFT 6722.In various examples, the blockchain system 6720 can include an NFTtransaction authenticator 6022, a secure real-time NFT metadatarepository 6024 and an NFT source 6026 that actually stores the gametoken NFT 6722 on a blockchain or other decentralized computersystem/network and user authentication/NFT validation can take place,for example as described in conjunction with FIGS. 12A-12D.

FIG. 16J presents a block diagram representation of an example system.This system operates similarly to the system of FIG. 16I, however, theapplication launch request 6732 is received directly from the wallet6725.

FIG. 16K presents a flowchart representation 6700-4 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6702-4 includesreceiving an application launch request for a game application having agame token NFT associated therewith. Step 6704-4 includes generating, inresponse to the application launch request, launch metadata. Step 6706-4includes sending the launch metadata to a wallet associated with a userof the client device, the wallet containing a private key associatedwith the game token NFT. Step 6708-4 includes receiving, from thewallet, a launch response that is generated based on the private key.Step 6710-4 includes generating, based on the launch response, anownership check. Step 6712-4 includes sending the ownership check to ablockchain system that stores the game token NFT. Step 6714-4 includesreceiving, from the blockchain system, an ownership validation response.Step 6716-4 includes enabling, via the game application, play of thegame when the ownership validation response indicates ownership of thegame token NFT is verified. Step 6718-4 includes preventing, via thegame application, play of the game when the ownership validationresponse indicates the ownership of the game token NFT is not verified.

FIG. 16L presents a block/flow diagram representation of an examplesystem. This example addresses a scenario where NFT's can be issuedin-application (in-app NFTs). These in-app NFTs can correspond to any ofthe game-collected NFTs and/or other collected or collectable items,achievements, purchased items, and or other NFTs that can be purchased,earned and/or collected in-app. For example, first launch for a new usercan issue an unsealing/open box NFT that is the digital equivalent ofopening the box of a physical good and collecting a prize. These in-appNFT's can be tied to the user/owner of the game token NFT 6722 and/ortied to a particular instance of the game application 6718. This allowssome NFTs to be transferred when ownership of the game application istransferred via sale or micro-loan of the game token NFT 6718. In otherexamples, the in-app NFTs can be independently sold and disassociatedwith the game token NFT 6722.

In various examples, the application execution device 6730 receives anin-app issuance request 6742 from a gaming application 6718 that wasgenerated either automatically or in response to user interaction withthe game. The application execution device 6730 responds byfacilitating, based on in-app NFT data 6744, the minting of an in-gameNFT 6745 associated with the electronic game based on an authenticationof the ownership of the game application 6718 via ownership of theassociated game token NFT 6722 by the user/owner that is playing thegame.

In various examples, the system operates by: generating, via theapplication execution device 6730, an ownership check 6736; sending theownership check 6736 to a blockchain system 6720 that stores a gametoken NFT 6722 associated with the electronic game and the user;receiving, from the blockchain system 6720, an ownership validationresponse 6738; and facilitating, via the game application 6718, aminting/issuance of the in-app NFT 6745 when the ownership validationresponse 6738 indicates ownership of the game token NFT 6722 isverified.

In this example shown, an ownership check 6736 is initiated not only onlaunch of the game application 6718, but also when an in-app issuancerequest 6742 is initiated to generate a in-app NFT. The in-app NFT 6745is only minted when a favorable ownership validation response 6738 isreceived indicating validated ownership and/or user authentication ofthe game token NFT 6722. Furthermore, a favorable payment response 6714may be required when the in-app issuance request 6742 has an associateda cost. Otherwise, if payment is denied or ownership validation fails,the requested in-app NFT 6745 is not minted.

FIG. 16M presents a flowchart representation 6700-5 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6702-5 includesreceiving, at the NFT platform and from a game application associatedwith an electronic game played by a user, an in-app issuance request foran in-app NFT. Step 6704-5 includes generating, via the NFT platform, anownership check. Step 6706-5 includes sending the ownership check to ablockchain system that stores a game token NFT associated with theelectronic game and the user. Step 6708-5 includes receiving, from theblockchain system, an ownership validation response. Step 6710-5includes facilitating, via the game application, issuance of the in-appNFT when the ownership validation response indicates ownership of thegame token NFT is verified.

FIG. 17A presents a pictorial representation of an example screendisplay. In various examples, one or more player token NFTs 6848 can bepurchased, collected or otherwise issued to a particular user of aclient device 825. The player token NFTs 6848, are specific examples ofgame token NFTs and can be used to provide authenticated access by theuser to a game that, for example can be executed and/or streamed to auser's client device in order for the user to play a particular game. Inaddition, player token NFTs are associated with a particular playerand/or the associated player/character used in the game. In thisfashion, a player token NFT 6848, while not associated with storage ofthe game application, nevertheless are associated with a user'sownership and/or control of and/or access to a particularplayer/character of game and can be used by a game application, clientdevice 825 and/or game platform 6625 to provide authenticated access bythe user to play the game—with the associated player/character.

In the example shown, the player token NFTs 6848-1, 6848-2, 6848-3 . . .are each associated with a different players associated with the gameCatacombs.

FIG. 17B presents a block diagram representation of an example system.The system includes a NFT platform 6825, such as NFT collection platform800, NFT game platform 6500, NFT distribution platform 2800 or other NFTplatform that operates to facilitate the creation of new NFTs such asgame NFTs or other NFTs associated with games or other media and/or theplay of games associated with one or more game NFTs that have beenpurchased or acquired by a player, collector or other user. The systemfurther includes a client device 825, a payment processor 6810 or othermarketplace or marketplace tool, a blockchain system 6820, such as NFTcreation system 824 or other decentralized computer system and a wallet6826, such as NFT wallet system 820 or other wallet.

A client device generates a purchase request 6802 for a player token NFT6822 associated with an electronic game that is received by the NFT gameplatform 6825. The NFT game platform 6825 responds by generating apayment request 6804 and receives a payment response 6814 indicatingwhether or not the payment request is verified. In various examples, inresponse to the payment response verifying the payment request, the NFTgame platform system 6825 facilitates the minting of a player token NFT6822 associated with the electronic game. In addition, or inalternative, one or more player token NFTs can be minted prior to sale.In this fashion, for example, a limited and/or numbered series of playertoken NFTs can be minted and offered for sale to collectors.Furthermore, pre-minting a number of NFTs for sale can help expedite thesales because the minting of the player token NFTs does not need tooccur in real-time.

In various examples, minting of the player token NFT 6822 includesgeneration of a private key associated with the player token NFT that isstored with NFT metadata and/or other wallet data 6826 in the wallet6826. In other examples, an existing private key can be retrieved andused for the same purpose. The player token NFT 6822 serves toauthenticate the purchase of the game or access to a game/tournament orgame application by the user of the client device 825 and can be used toenable play of the electronic game via the client device 825, forexample, by verification of the NFT authorization before the game isfully launched for game play via the client device 825. This improvesthe technology of game systems by providing a secure and incorruptiblemethodology for authenticating game/tournament access and/orauthenticating the user to the game as the actual game owner or otherauthorized user/player and/or associated character. While a particulararchitecture is shown, other configurations, combinations andconnections are likewise possible. Furthermore, other authenticationsystems & methodologies described herein, including any of thetechniques described in conjunction with FIGS. 12A-12D, could likewisebe employed.

FIG. 17C presents a flowchart representation 6800-1 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6802-1 includesreceiving, at the NFT platform and from a client device, a purchaserequest for a player token NFT associated with an electronic game. Step6804-1 includes generating a payment request in response to the purchaserequest. Step 6806-1 includes receiving a payment response verifying thepayment request. Step 6808-1 includes facilitating, in response to thepayment response verifying the payment request, via the processor,issuance of a player token NFT associated with the electronic game forenabling play of the electronic game.

FIG. 17D presents a block/flow diagram representation of an examplesystem. In this example, ownership (e.g. authenticated ownership) by auser of one or more non-game NFTs 6821-2 is used to automaticallytrigger the generation of a player token NFT 6824-2 based on other data6822-2. As used herein, a non-game NFT is an NFT that, even though itmay provide benefits to a particular game and have value to collectorsindependent of a particular, it is not specific to a particular game. Inthis fashion, a game studio may issue NFTs that provide subsidiarybenefits to a number of different games as opposed to one specific game.For example, one or more non-game NFTs 6821-2 associated with InMotionGames, may provide benefits to a number of different games produced byInMotion, as opposed to any one specific game.

In the example shown in FIG. 17E, after a non-game NFTs 6821-2associated with InMotion Games is authenticated to the user, playertoken NFTs 6824-2 are generated as a result. While ownership/collectionof a single NFT triggers generation of multiple player token NFTs, inother examples, ownership collection of multiple non-game NFTs may berequired to generate either a single player token NFT or a series ofplayer token NFTs associated with a single game or different games.

In this fashion, a non-game NFT associated with a film or series offilms, may provide benefits to a particular game that is based oncharacters from the film(s), even though it is primarily associated withthe film(s) themselves. For example, a non-game NFT associated withHarry Potter series of films may provide benefits to a particular gamethat is based on characters from the Harry Potter film(s), even thoughthe NFT is primarily associated with the film(s) themselves. In thisfashion, a non-game NFT associated with an unrelated product, mayprovide benefits to a particular game that is sponsored by the producerof this product. For example, a Fritos NFT may provide benefits to aparticular game that is sponsored by Frito-Lay.

In this context, the other data 6822-2 can include the particular imageto be associated with the player token NFT 6824-2 along with other dataused in NFT generation as previously described herein.

FIG. 17F presents a flowchart representation 6800-2 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6802-2 includesdetermining, via the processor, when one or more non-game NFTs areauthenticated. Step 6804-2 includes receiving, via the processor, otherdata, wherein the other data is associated with a player token NFT to begenerated. Step 6806-2 includes facilitating creation of the playertoken NFT based on the other data, when the one or more non-game NFTsassociated with the multiplayer game are authenticated.

FIG. 17G presents a block/flow diagram representation of an examplesystem. In this example, ownership (e.g. authenticated ownership) by auser of one or more game-collected NFTs 6821-3 is used to automaticallytrigger the generation of a player token NFT 6824-3 based on other data6822-3. As used herein, a game collected NFT is an NFT that wascollected via play/use of a game to be associated with the player token.In the example shown in FIG. 17H, after a user/player has collected NFTs6821-3 via play of Catacombs, and these NFTs are authenticated to theuser, player token NFT 6824-2 is generated as a result. In this fashion,a user can collect new player tokens to a game that can be used infuture play if older player tokens to that game expire after a time ordue to the loss of the game by a player.

FIG. 17I presents a flowchart representation 6800-3 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6802-3 includesdetermining, via the processor, when one or more game-collected NFTsassociated with a multiplayer game are authenticated. Step 6804-3includes receiving, via the processor, other data, wherein the otherdata is associated with a player token NFT to be generated. Step 6806-3includes facilitating creation (e.g., issuance) of the player token NFTbased on the other data, when the one or more game-collected NFTsassociated with the multiplayer game are authenticated.

FIGS. 17J-17K present a block/flow diagram representations of examplesystems. In the example shown in FIG. 17J, an application executiondevice 6830 stores the game application 6818 for execution having aplayer token NFT 6822 associated therewith. Similar devices shown inFIG. 17B are represented by similar reference numerals. The applicationexecution device can be a client device 825, an NFT platform 800, NFTgame platform 6625 or other NFT platform or other device for executingthe game application 6818 to facilitate play of the game.

In operation, the application execution device 6830 operates in responseto application launch request 6832 for the game application 6818. Thisapplication launch request 6832 can be received (internally) from a userinterface associated with the application execution device 6830 (e.g. aclient device or NFT platform) and/or received from an external devicesuch as a client device, when for example, the application executiondevice 6830 corresponds to an NFT platform in communication with aclient device. Once execution of the gaming application is initiated inresponse to the application launch request 6832, launch metadata 6834 isgenerated, for example, to determine if the launch request can bevalidated. The launch metadata 6834 is sent to the wallet 6825containing a private key associated with the player token NFT 6822associated with a user, such as a user of the application executiondevice and/or the application execution device 6830. The applicationexecution device 6830 receives from the wallet 6826, a launch response6835 that is generated based on the private key. The game applicationgenerates, based on the launch response 6836, an ownership check 6836that is sent to the blockchain system 6820 that stores the player tokenNFT 6822. An ownership validation response 6838 is received from theblockchain system 6820 that enables play of the game via the gameapplication 6818 when the ownership validation response 6838 indicatesownership of the player token NFT is verified and prevents play of thegame via the game application 6818 when the ownership validationresponse 6838 indicates ownership of the player token NFT is notverified. When not verified, the game application 6818 can, for example,shut itself down. In this fashion, the game application 6818 canself-validate on launch to verify ownership/authorized use by the userusing player token NFT data in a user's wallet which holds the privatekey to the player token NFT 6822.

In various examples, the launch metadata 6834 can include a current dateand time, expiration information (if any) and a version number of thegame application 6818, a counter that indicates a number of times theapplication has been executed, and/or other data corresponding to theplayer token NFT 6822, the game application 6818 and/or the launch. Thelaunch response 6835 can include a public key associated with the playertoken NFT 6822, a signed hash that is based on the private key, thelaunch metadata 6834, and/or other data/metadata to be used to validatethe NFT data from the wallet 6825 to the player token NFT 6822. In thisfashion, the private key is not shared directly with the applicationbinary—and instead is merely used by the wallet 6825 in a securefashion.

The ownership check 6836 can include information from the launchresponse 6835, additional owner/user information, such as userauthentication data, associated with the user and/or owner of the playertoken NFT 6822 and or other and/or other data/metadata to be used tovalidate the NFT data from the wallet 6825 to the player token NFT 6822.In various examples, the blockchain system 6820 can include an NFTtransaction authenticator 6022, a secure real-time NFT metadatarepository 6024 and an NFT source 6026 that actually stores the playertoken NFT 6822 on a blockchain or other decentralized computersystem/network and user authentication/NFT validation can take place,for example as described in conjunction with FIGS. 12A-12D.

FIG. 17K presents a block diagram representation of an example system.This system operates similarly to the system of FIG. 17I, however, theapplication launch request 6832 is received directly from the wallet6825.

FIG. 17L presents a flowchart representation 6800-4 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6802-4 includesreceiving an application launch request for a game application having aplayer token NFT associated therewith. Step 6804-4 includes generating,in response to the application launch request, launch metadata. Step6806-4 includes sending the launch metadata to a wallet associated witha user of the client device, the wallet containing a private keyassociated with the player token NFT. Step 6808-4 includes receiving,from the wallet, a launch response that is generated based on theprivate key. Step 6810-4 includes generating, based on the launchresponse, an ownership check. Step 6812-4 includes sending the ownershipcheck to a blockchain system that stores the player token NFT. Step6814-4 includes receiving, from the blockchain system, an ownershipvalidation response. Step 6816-4 includes enabling, via the gameapplication, play of the game when the ownership validation responseindicates ownership of the player token NFT is verified. Step 6818-4includes preventing, via the game application, play of the game when theownership validation response indicates the ownership of the playertoken NFT is not verified.

FIG. 17M presents a block/flow diagram representation of an examplesystem. This example addresses a scenario where NFT's can be issuedin-application (in-app NFTs). These in-app NFTs can correspond togame-collected NFTs and/or other collected or collectable items,achievements, purchased items, and or other NFTs that can be purchasedor collected in-app. For example, first launch for a new user can issuean unsealing/open box NFT that is the digital equivalent of opening thebox of a physical good and collecting a prize. These in-app NFT's can betied to the user/owner of the player token NFT 6822 and/or tied to aparticular instance of the game application 6818. This allows some NFTsto be transferred when ownership of the game application is transferredvia sale or micro-loan of the player token NFT 6818. In other examples,the in-app NFTs can be independently sold and disassociated with theplayer token NFT 6822.

In various examples, the application execution device 6830 receives anin-app issuance request 6842 from a gaming application 6818 that wasgenerated either automatically or in response to user interaction withthe game. The application execution device 6830 responds byfacilitating, based on in-app NFT data 6844, the minting of an in-gameNFT 6845 associated with the electronic game based on an authenticationof the ownership of the game application 6818 via ownership of theassociated player token NFT 6822 by the user/owner that is playing thegame.

In various examples, the system operates by: generating, via theapplication execution device 6830, an ownership check 6836; sending theownership check 6836 to a blockchain system 6820 that stores a playertoken NFT 6822 associated with the electronic game and the user;receiving, from the blockchain system 6820, an ownership validationresponse 6838; and facilitating, via the game application 6818, aminting/issuance of the in-app NFT 6845 when the ownership validationresponse 6838 indicates ownership of the player token NFT 6822 isverified.

In this example shown, an ownership check 6836 is initiated not only onlaunch of the game application 6818, but also when an in-app issuancerequest 6842 is initiated to generate a in-app NFT. The in-app NFT 6845is only minted when a favorable ownership validation response 6838 isreceived indicating validated ownership and/or user authentication ofthe player token NFT 6822. Furthermore, a favorable payment response6814 may be required when the in-app issuance request 6842 has anassociated a cost. Otherwise, if payment is denied or ownershipvalidation fails, the requested in-app NFT 6845 is not minted.

FIG. 17N presents a flowchart representation 6800-5 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6802-5 includesreceiving, at the NFT platform and from a game application associatedwith an electronic game played by a user, an in-app issuance request foran in-app NFT. Step 6804-5 includes generating, via the NFT platform, anownership check. Step 6806-5 includes sending the ownership check to ablockchain system that stores a player token NFT associated with theelectronic game and the user. Step 6808-5 includes receiving, from theblockchain system, an ownership validation response. Step 6810-5includes facilitating, via the game application, issuance of the in-appNFT when the ownership validation response indicates ownership of theplayer token NFT is verified.

FIG. 18A presents a block/flow diagram representation of an examplesystem of an example of NFT generation. In the example shown, NFTgeneration tools 808 operate to convert image data 6920-1 and other data6922-1 (including persona data) into one or more player token NFTs6924-1. The image data 6920-1 can correspond to an original NFT,borrowed (e.g. temporary micro-loaned) NFT, a derivative NFT, anoriginal image, and/or other derivatives or micro-loans thereof or otherdisplay or image data. In various examples, the NFT generation tools 808can operate to verify the credentials of any NFTs whose images arecontained in the image data 6920-1, prior to creating the player tokenNFT 6924-1. In this fashion, one or more player token NFTs 6924-1 canonly be created (e.g. on a derivative basis) when the source NFT or NFTsare verified—preventing the creation of unauthorized or counterfeitNFTs.

The other data 6922-1, can include a set of persona data correspondingto a set of players having differing personas with, for example,differing attributes, abilities, strengths, weaknesses and/or otherproperties in a game. These properties can include personas with differgoals including some personas having a goal to win, some personas havinga goal to sabotage and/or spoil the victory for other players, otherpersonas having a goal to extend the game as long as possible, etc. Theother data 6922-1 can further include image data including signaturesand other endorsement images, visual indications of derivative series,originality classification, attributions, or other image data, metadataof all kinds including metadata indicating one or more originalityclassifications, attributions, endorsement data, other derivative dataindicating the series number and total number in a derivative series,restrictions on micro-loans or other derivatives, restrictions onderivatives with artistic effects, restrictions that derivatives mustinclude attributions to the original source, restrictions on numbers ofderivatives or micro-loans or the sizes of derivative series,restrictions on the creation of collection NFTs, the number ofcollection NFTs, the creation of collection NFTs including NFTs fromother sources, from prohibited sources or with prohibited content,geographical restrictions, time restrictions (e.g., can be used tocreate derivatives or collection NFTs or can be temporarily micro-loanedfor 1 month, one year, etc., other restrictions and/or other dataassociated with, or to be associated with, the image data 6920-1.

This other data 6922-1 can be used to generate an NFT and/or combinedwith the image data 6920-1 to create a dataset that includes both theimage data 6920-1 and the other data 6922-1. This other data 6922-1 orcombined dataset can be protected via the blockchain and/or othercrypto-based NFT creation technology that is employed by the NFTgeneration tools 808 and via the NFT creation system 824 to create andprotect each new player token NFT 6924-1 itself. It should be noted thatthe player token NFTs 6924-1 can include a single derivative or a numberof derivatives, including a limited series of derivatives. It should benoted further that some or all of the other data 6922-1, includingrestriction data and/or attribution data, can be derived from one ormore original NFTs whose images are associated with the image data6920-1.

In various embodiments, the player token NFTs can be selected by a user,or assigned randomly, at time of purchase or at the time the playertoken NFT is first used. Player token NFTs can be collected by user viaprior game play, earned via collection of one or more required non-gameor game-collected NFTs, or other wise bought, sold traded, collected,etc.

FIG. 18B presents a flowchart representation 6900-1 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-1 includesreceiving, via the processor, an image to be associated with a series ofplayer token NFTs corresponding to a multiplayer game. Step 6904-1includes receiving, via the processor, other data, wherein the otherdata including persona data is also associated with the series of playertoken NFTs. Step 6906-1 includes facilitating creation of the series ofplayer token NFTs.

FIGS. 18C-18D present a block/flow diagram representations of examplesystems. As previously discussed, ownership and/or authenticationnon-game NFTs can be used to trigger the generation of game token NFTs,player token NFTs and/or with other NFTs that are related to agame/tournament and/or game application. In addition, ownership and/orauthentication can be non-game NFTs can, in addition or in thealternative, be used to trigger the augmentation of a particularplayer/character in a game with special attributes, abilities,strengths, weaknesses and/or other properties in a game.

In the example shown in FIG. 18C, an application execution device 6930stores the game application 6918 for execution having a player token NFT6922 associated therewith. The application execution device can be aclient device 825, an NFT platform 800, NFT game platform 6625 or otherNFT platform or other device for executing the game application 6918 tofacilitate play of the game.

In operation, the application execution device 6930 operates in responseto an application launch request 6932 for the game application 6918.This application launch request 6932 can be received (internally) from auser interface associated with the application execution device 6930(e.g. a client device or NFT platform) and/or received from an externaldevice such as a client device, when for example, the applicationexecution device 6930 corresponds to an NFT platform in communicationwith a client device. Once execution of the gaming application isinitiated in response to the application launch request 6932, launchmetadata 6934 is generated, for example, to determine if the launchrequest is associated with a valid non-game NFT. The launch metadata6934 is sent to the wallet 6925 containing a private key associated withthe non-game NFT 6922-1 associated with a user, such as a user of theapplication execution device and/or the application execution device6930. The application execution device 6930 receives from the wallet6926, a launch response 6935 that is generated based on the private key.The game application generates, based on the launch response 6936, anownership check 6936 that is sent to the blockchain system 6920 thatstores the non-game NFT 6922-1. An ownership validation response 6938 isreceived from the blockchain system 6920 that augments aplayer/character via the game application 6918 when the ownershipvalidation response 6938 indicates ownership of the non-game NFT 6922-1is verified and does not augment the player/character via the gameapplication 6918 when the ownership validation response 6938 indicatesownership of the player token NFT is not verified.

In various examples, the launch metadata 6934 can include a current dateand time, expiration information (if any) and a version number of thegame application 6918, a counter that indicates a number of times theapplication has been executed, and/or other data corresponding to thenon-game NFT 6922-1, the game application 6918 and/or the launch. Thelaunch response 6935 can include a public key associated with thenon-game NFT 6922-1, a signed hash that is based on the private key, thelaunch metadata 6934, and/or other data/metadata to be used to validatethe NFT data from the wallet 6925 to the non-game NFT 6922-1. In thisfashion, the private key is not shared directly with the applicationbinary—and instead is merely used by the wallet 6925 in a securefashion.

The ownership check 6936 can include information from the launchresponse 6935, additional owner/user information, such as userauthentication data, associated with the user and/or owner of thenon-game NFT 6922-1 and or other and/or other data/metadata to be usedto validate the NFT data from the wallet 6925 to the non-game NFT6922-1. In various examples, the blockchain system 6920 can include anNFT transaction authenticator 6022, a secure real-time NFT metadatarepository 6024 and an NFT source 6026 that actually stores the playertoken NFT 6922 on a blockchain or other decentralized computersystem/network and user authentication/NFT validation can take place,for example as described in conjunction with FIGS. 12A-12D. Furthermore,while not expressly shown, the process described above can also includevalidation of a game token NFT and/or player token NFT as a requirementto successfully launch the game application.

FIG. 18D presents a block diagram representation of an example system.This system operates similarly to the system of FIG. 18C, however, theapplication launch request 6932 is received directly from the wallet6925.

FIG. 18E presents a flowchart representation 6900-2 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-2 includesreceiving an application launch request for a game application having anon-game NFT associated therewith. Step 6904-2 includes generating, inresponse to the application launch request, launch metadata. Step 6906-2includes sending the launch metadata to a wallet associated with a userof the client device, the wallet containing a private key associatedwith the non-game NFT. Step 6908-2 includes receiving, from the wallet,a launch response that is generated based on the private key. Step6910-2 includes generating, based on the launch response, an ownershipcheck. Step 6912-2 includes sending the ownership check to a blockchainsystem that stores the non-game NFT. Step 6914-2 includes receiving,from the blockchain system, an ownership validation response. Step6916-2 includes augmenting, via the game application, a game player'sgame abilities when the ownership validation response indicatesownership of the non-game NFT is verified.

FIG. 18F presents a block/flow diagram representation of an examplesystem. In the example shown, NFT generation tools can be used togenerate an updated player token NFT 6921-3 that is based on a playertoken NFT 6920-3 and game data 6926-3 generated via play of the game viathe player/character associated with the player token NFT 6920-3. Inthis fashion, game data 6926 indicating new abilities, enhancements,achievements, stats, experience, level-ups, level-downs, scores, statusor other game performance metrics earned and/or otherwise occurring viathe game can be stored on the blockchain or other decentralized computernetwork with the original player token NFT 6920-3 to generate an updatedplayer token NFT 6221-3 as a derivative NFT or entirely new NFT thatsupersedes the prior NFT.

FIG. 18G presents a flowchart representation 6900-3 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-3 includesfacilitating, via a processor, play of a game based on a player tokenNFT associated with the game. Step 6904-3 includes updating the playertoken NFT associated with the game, based on game data associated withthe game play by a player associated with the player token NFT.

FIG. 18H presents a block/flow diagram representation of an examplesystem. In the example shown, NFT generation tools can be used togenerate an updated game token NFT 6921-4 that is based on a game tokenNFT 6920-4 and game data 6926-4 generated via play of the game via theplayer/character associated with the game token NFT 6920-4. In thisfashion, game data 6926 indicating new abilities, enhancements,achievements, stats, experience, level-ups, level-downs, scores, statusor other game performance metrics earned and/or otherwise occurring viathe game can be stored on the blockchain or other decentralized computernetwork with the original game token NFT 6920-4 to generate an updatedgame token NFT 6221-4 as a derivative NFT or entirely new NFT thatsupersedes the prior NFT.

FIG. 18I presents a flowchart representation 6900-4 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-4 includesfacilitating, via a processor, play of a game based on a game token NFTassociated with the game. Step 6904-4 includes updating the game tokenNFT associated with the game, based on game data associated with thegame play by a player associated with the game token NFT.

FIG. 18J presents a flowchart representation 6900-5 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. As a supplementalcase of the system of FIG. 18F, game data 6926-3 may indicate that aplayer has lost a game/tournament or “died” in the game. In the responseto this condition, instead of issuing an updated player token NFT, theplayer token NFT6920-3 may, based for example on the restrictionsassociated with the NFT, be terminated, expired or otherwiseburned—optionally maintaining, for example, the NFT for collectionpurposes, while preventing the future use of the player token NFT6920-3for enabling game play.

Step 6902-5 includes facilitating, via a processor, play of a game basedon a player token NFT associated with the game. Step 6904-5 includesexpiring the player token NFT associated with the game, when game dataassociated with the game play indicates a loss by a player associatedwith the player token NFT.

FIG. 18K presents a flowchart representation 6900-6 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. As a supplementalcase of the system of FIG. 18H, game data 6926-4 may indicate that aplayer has lost a game/tournament or “died” in the game. In the responseto this condition, instead of issuing an updated game token NFT, thegame token NFT6920-3 may, based for example on the restrictionsassociated with the NFT, be terminated, expired or otherwiseburned—optionally maintaining, for example, the NFT for collectionpurposes, while preventing the future use of the game token NFT6920-3for enabling game play.

Step 6902-6 includes facilitating, via a processor, play of a game basedon a game token NFT associated with the game. Step 6904-6 includesexpiring the game token NFT associated with the game, when game dataassociated with the game play indicates a loss by a player associatedwith the game token NFT.

FIGS. 18L-18M present a block/flow diagram representations of examplesystems. In particular, these systems operate similarly to the systemsof FIGS. 17J and 17K to enable tournament play, rather than normal gameplay via a player token 6922-7.

FIG. 18N presents a flowchart representation 6900-7 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-7 includesreceiving a tournament entry request for a game application having aplayer token NFT associated therewith. Step 6904-7 includes generating,in response to the application launch request, launch metadata. Step6906-7 includes sending the launch metadata to a wallet associated witha user of the client device, the wallet containing a private keyassociated with the player token NFT. Step 6908-7 includes receiving,from the wallet, a launch response that is generated based on theprivate key. Step 6910-7 includes generating, based on the launchresponse, an ownership check. Step 6912-7 includes sending the ownershipcheck to a blockchain system that stores the player token NFT. Step6914-7 includes receiving, from the blockchain system, an ownershipvalidation response. Step 6916-7 includes enabling, via the gameapplication, play in the tournament when the ownership validationresponse indicates ownership of the player token NFT is verified. Step6918-7 includes preventing, via the game application, play in thetournament when the ownership validation response indicates theownership of the player token NFT is not verified.

FIGS. 18O-18P present a block/flow diagram representations of examplesystems. In particular, these systems operate similarly to the systemsof FIGS. 16I and 16J to enable tournament play, rather than normal gameplay via a game token 6922-8.

FIG. 18Q presents a flowchart representation 6900-8 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-8 includesreceiving a tournament entry request for a game application having agame token NFT associated therewith. Step 6904-8 includes generating, inresponse to the application launch request, launch metadata. Step 6906-8includes sending the launch metadata to a wallet associated with a userof the client device, the wallet containing a private key associatedwith the game token NFT. Step 6908-8 includes receiving, from thewallet, a launch response that is generated based on the private key.Step 6910-8 includes generating, based on the launch response, anownership check. Step 6912-8 includes sending the ownership check to ablockchain system that stores the game token NFT. Step 6914-8 includesreceiving, from the blockchain system, an ownership validation response.Step 6916-8 includes enabling, via the game application, play of in thetournament when the ownership validation response indicates ownership ofthe game token NFT is verified. Step 6918-8 includes preventing, via thegame application, play in the tournament when the ownership validationresponse indicates the ownership of the game token NFT is not verified.

FIG. 18R presents a flowchart representation 6900-9 of an examplemethod. In particular, a method is presented for use in conjunction withone or more functions or features described herein. Step 6902-9 includesreceiving a start game request for game corresponding to a gameapplication having a player token NFT associated therewith. Step 6904-9includes generating launch metadata. Step 6906-9 includes sending thelaunch metadata to a wallet associated with a user of a client device,the wallet containing a private key associated with the player tokenNFT. Step 6908-9 includes receiving, from the wallet, a launch responsethat is generated based on the private key. Step 6910-9 includesgenerating, based on the launch response, ownership check data.

Step 6912-9 includes sending the ownership check data to a blockchainsystem that stores the player token NFT. Step 6914-9 includes receiving,from the blockchain system, an ownership validation response. Step6916-9 includes enabling, via the game application, play of a gameassociated with the game application when the ownership validationresponse indicates ownership of the player token NFT is verified. Step6918-9 includes preventing, via the game application, the play of thegame when the ownership validation response indicates the ownership ofthe player token NFT is not verified.

In various examples, the ownership check data includes at least one of:NFT identification data associated with the player token NFT or NFTauthentication data generated based on the private key. The ownershipcheck data can further include user identification data associated withthe user of the client device. The ownership validation response canindicate ownership of the player token NFT is verified when the playertoken NFT is authenticated based on the NFT authentication data and whenthe user of the client device is identified based on the useridentification data. The user identification data associated with theuser of the client device can include at least one of: a user deviceidentifier associated with the client device or user biometric datagenerated via the client device.

In various examples, the player token NFT has an associated playerpersona of a plurality of player personas associated with the game. Theownership validation response can indicate whether or not ownership ofthe player token NFT is verified. The ownership validation response caninclude credentials data to enable the play of the game via a playertoken associated with the player token NFT when the ownership of theplayer token NFT is verified.

The start game request can includes an application launch request or arequest to start or enter a game associated with a game application thathas already been launched. The player token NFT can be expended (e.g.terminated, burned and/or deactivated) based on game play dataassociated with player token that indicates loss of the game.

FIG. 19A presents a pictorial representation of an example item. In theexample shown, a purchased item 7022 includes an optical code such asthe QR code that is shown that provides a link to an associated gametoken NFT that, for example, is generated to be associated with the gametoken that can be collected and used to play a game. In addition to anyof the games previously discussed including online games and traditionalgaming apps, in various examples, the game token can correspond to apromotional game that provides a discount, free sample, promotionalbenefit and/or other reward associated with a product or service. In theexample shown, a drink cup includes a QR code that allows a user toaccess a game token NFT associated with a promotion Monopoly game taken.While the QR code is shown to be exposed in the example shown, in otherexamples, the QR codes could be covered and only revealed when acovering layer is pealed or scratched off. In various examples, thecoupons could be included with the items themselves and/or printed on areceipt for each item by a POS terminal or other device, verifying thatthe item has been purchased.

FIG. 19B presents a pictorial representation of an example clientdevice. In the example shown, the user of the client device has scannedthe QR code and collected the game token NFT for later redemption. Inparticular, the game token NFT can be stored in a wallet, such as acrypto/NFT wallet associated with the user and implemented via anapplication of the client device. As previously discussed, unlike anormal wallet, which can physically hold cash, credit cards, etc., NFTwallets “store” NFTs by storing the NFT data necessary to access theNFT. So, even though a wallet can be said to store an NFT, technicallythe NFT content is stored on the blockchain, which can only be accessedvia the NFT data in the wallet.

While the foregoing has focused on the use of QR codes in associationwith the distribution of game token NFTs, other types of codes such asbar codes, numerical codes, alphanumeric codes, alphabetic codes,symbolic codes and/or other identification data can beread/scanned/entered and/or wireless received in order to provide accessto a game token NFT or other NFT in a similar fashion.

FIG. 19C presents a flowchart representation 7000 of an example method.In particular, a method is presented for use in conjunction with an NFTplatform or system and/or any of the other functions and featurespreviously described. In various examples, a method is presented for usewith a non-fungible token (NFT) client device that includes a processorand a memory and that utilizes a graphical user interface to interactwith a user.

Step 7002 includes reading, via the client device, an optical codeassociated with a game token. Step 7004 includes sending, via the clientdevice and in response to reading the optical code, a request todownload a game token NFT associated with the game token from an NFTdistribution platform. Step 7006 includes receiving from the NFTdistribution platform, via the client device, the game token NFTassociated with the game token. Step 7008 includes storing the gametoken NFT in a wallet associated with a user of the client device.

FIGS. 20A-20B present pictorial representations of example items inaccordance with the example promotion involving the collection of aspecific set of game tokens. Consider an example where the game tokensare generated for a promotion where, as selected items are purchased,corresponding game token NFTs can be collected. When one or morepredetermined sets of corresponding game NFTs are collected, thecollection of all of the game token NFTs in the set can be used totrigger/unlock the acquisition of an asset or other reward such as anamount of cash, an amount of crypto currency, a limited edition NFT, aspecial bonus item, a game piece or other game item, a product, apurchase discount and/or other award.

The items 7222-1 and 7222-2 are presented in the form of a drink cup anda French fry container and each include links to a corresponding gametoken NFT. While shown as individual items and QR codes, in otherexamples, these can be combined with multiple items being represented bya single coupon/QR code when all or some proper subset of the items arepurchased together. As previously discussed, the use of QR codes inassociation with the distribution of coupon NFTs, other types of codessuch as bar codes, numerical codes, alphanumeric codes, alphabeticcodes, symbolic codes and/or codes can be read/scanned/entered and/orwireless received in order to provide access to a game token NFT orother NFT in a similar fashion.

FIGS. 20C-20D present pictorial representations of an example clientdevice. In FIG. the user has purchased french fries and a drink andconsequently has been able to download two game token NFTs. In theexample shown, these game token NFTs each correspond to a differentrailroad token in a Monopoly game promotion. In FIG. 20D, all 4 gametoken NFTs in a set (corresponding to all four railroads) required bythe promotion have been downloaded, collected and authenticated,facilitating the redemption of the corresponding reward in accordancewith the promotion.

FIG. 20E presents a flowchart representation of an example method. Inparticular, a method 7200-1 is presented for use in conjunction with anNFT platform or system and/or any of the other functions and featurespreviously described. In various examples, a method is presented for usewith a non-fungible token (NFT) client device that includes a processorand a memory and that utilizes a graphical user interface to interactwith a user.

Step 7202-1 includes reading, via a client device, via an optical codeassociated with a game token. Step 7204-1 includes sending, via theclient device and in response to reading the optical code, a request todownload a game token NFT associated with the game token to an NFTdistribution platform. Step 7406-1 includes receiving from the NFTdistribution platform, via the client device, the game token NFTassociated with a game token. Step 7408-1 includes determining when theclient device has downloaded game token NFTs associated with each gametoken of a series of game tokens. Step 7210-1 includes facilitating agame utilizing the series of game tokens, via the client device, whenthe client device has downloaded game token NFTs associated with eachgame token of the series of game tokens.

FIG. 20F presents a flowchart representation of an example method. Inparticular, a method 7200-2 is presented for use in conjunction with anNFT platform or system and/or any of the other functions and featurespreviously described. In various examples, a method is presented for usewith a non-fungible token (NFT) client device that includes a processorand a memory and that utilizes a graphical user interface to interactwith a user.

Step 7202-2 includes reading, via a client device, via an optical codeassociated with a game token. Step 7204-2 includes sending, via theclient device and in response to reading the optical code, a request todownload a game token NFT associated with the game token to an NFTdistribution platform. Step 7206-2 includes receiving from the NFTdistribution platform, via the client device, the game token NFTassociated with the game token. Step 7208-2 includes determining whenthe client device has downloaded game token NFTs associated with eachgame token of a series of game tokens. Step 7210-2 includes facilitatinga redemption transaction utilizing the series of game tokens, via theclient device, when the client device has downloaded game token NFTsassociated with each game token of the series of game tokens.

FIG. 20G presents a flowchart representation of an example method. Inparticular, a method 7200-3 is presented for use in conjunction with anNFT platform or system and/or any of the other functions and featurespreviously described. In various examples, a method is presented for usewith a non-fungible token (NFT) client device that includes a processorand a memory and that utilizes a graphical user interface to interactwith a user.

Step 7202-3 includes receiving, at the processor, a transaction requestto redeem a plurality of game token NFTs minted via a blockchain,wherein the transaction request includes game token NFT identificationdata identifying the game token NFTs. Step 7204-3 includes determining,via the processor, when the game token NFTs are authenticated. Step7206-3 includes generating credentials data to grant the transactionrequest when the game token NFTs are authenticated.

FIG. 20H presents a flowchart representation of an example method. Inparticular, a method 7200-4 is presented for use in conjunction with anNFT platform or system and/or any of the other functions and featurespreviously described. In various examples, a method is presented for usewith a non-fungible token (NFT) client device that includes a processorand a memory and that utilizes a graphical user interface to interactwith a user.

Step 7202-4 includes receiving, at the processor, a transaction requestto redeem a plurality of game token NFTs minted via a blockchain,wherein the transaction request includes game token NFT identificationdata identifying the game token NFTs received via a wallet of an ownerof the plurality of game token NFTs. Step 7204-4 includes determining,via the processor, when the game token NFTs are authenticated. Step7206-4 includes generating credentials data to grant the transactionrequest when the game token NFTs are authenticated.

FIG. 21A presents a block diagram representation of an example system.The system includes a example of a point of sale (POS) platform 7127that can be implemented in conjunction with an NFT collection platform800, NFT distribution platform 2800 or other NFT platform that operatesto facilitate the creation and distribution of new NFTs such as gametoken NFTs 7122 or other NFTs associated with items purchased via thePOS system. In addition, the POS platform 7127 can be further used toauthenticate game token NFTs in association with sale of an item and/orother transaction such as the redemption of a reward associated with agame token NFT or a series of game tokens.

The POS platform 7127 includes a processor 7101, a memory 7103, anoptical scanner (O/S) 7105, a network interface 7107 for communicatingwith other portions of the system via a network, and a user interface7109 such as a display screen, touch screen, one or more buttons, akeyboard and/or keypad, an NFC interface or other wireless interface, acard scanner, a chip reader and/or one or more other interface devicesfor sending/receiving information to/from a user (e.g. a purchaser). Thesystem further includes an item database 6812 containing SKUs and itemdata associated with items that are for sale, a payment processor 6810or other marketplace or marketplace tool, a blockchain system 6820, suchas NFT creation system 824 or other decentralized computer system and awallet 6825, such as NFT wallet system 820, a wallet applicationassociated with client device 825 or other electronic wallet.

In an example of operation, the POS system 7127 operates by:

-   -   receiving, via the optical scanner 7105, image data        corresponding to a stock keeping unit (SKU) of an item;    -   receiving item data, via the network interface 7107 and        responsive to the SKU, wherein the item data is associated with        the item;    -   receiving, via the user interface 7109, payment information        associated with purchase of the item and processing payment;    -   facilitating, via the processor 7101, creation of a game token        NFT 7122 corresponding to the item; and    -   sending the game token NFT 7122 to a client device associated        with a purchaser of the item for storage in a wallet 7125        associated with the purchaser.

In a further example, the POS system 7127 receives, via the opticalscanner 7105, image data (e.g., optical data generated by the scanner inresponse to a bar code, QR code or other item identifier) correspondingto a stock keeping unit (SKU) 7106 of one or more items to be purchased.The SKU 7106 is sent to the item database 7112 via the network interface7107. Item data 7116 is received, via the network interface 7107 andresponsive to the SKU 7106. The item data 7116 is associated with theitem to be purchased and can include one or more images or other mediaassociated with the item, a model number, manufacturer, price, warrantyinformation, vender information and/or other data associated with theitem. The POS platform 7127 receives wallet ID data 7123 from the wallet7125 that indicates a game token NFT that can be authenticated via thePOS platform 7127 and/or blockchain system 7120. In this fashion, thegame token NFT 7022 (once authenticated) can be used in the event thegame token applies a discount, promotion or other award that is properlyassociated with the purchase of the item or items. For example, the gametoken NFT can be used in lieu of, or in addition to, traditional paymentinformation 7108 to complete a sale of the item or items—depending on ifan award condition has been met. In circumstances where the game tokenNFT provides a benefit that is limited to the purchase of certainitem(s) and/or certain purchase terms and conditions and/or limits,etc., this process can include, for example, correlating game tokeninformation from the game token NFT to the item or items to be purchasedto verify that the reward, in fact, applies to the proposed purchasetransaction.

While discussed above in terms of a single game token, a similar processcould be applied to a series of game tokens corresponding to apredetermined set that has been collected by the user. In FIG. 21B, theuser has completed the purchase of an item via the POS system and a gametoken NFT has been downloaded to the purchaser's wallet corresponding toa Park Place token as part of a Monopoly game promotion. Collecting theBoardwalk token later will complete a set and unlock a reward that canbe authenticated based on the presence of both game token NFTs in theuser's wallet.

FIG. 21C presents a flowchart representation of an example method. Inparticular, a method 7100-1 is presented for use in conjunction with anNFT platform or system and/or any of the other functions and featurespreviously described. In various examples, a is presented method for usewith a POS system and/or a non-fungible token (NFT) platform thatincludes a processor and a memory.

Step 7102-1 includes receiving, via the optical scanner, image datacorresponding to a stock keeping unit (SKU) of an item. Step 7104-1includes receiving item data, via the network interface and responsiveto the SKU, wherein the item data is associated with the item. Step7106-1 includes receiving, via the user interface, payment informationassociated with purchase of the item. Step 7108-1 includes facilitating,via the processor, creation of a game token NFT corresponding to theitem. Step 7110-1 includes sending the game token NFT to a client deviceassociated with a purchaser of the item for storage in a walletassociated with the purchaser.

As used herein, the terms “game piece” and “game character” can be usedinterchangeably to refer to a game character, an ancillary article orother article or object that is used in a game.

As used herein “blockchain” and “blockchain node” refer to traditionalblockchain technology. However, other decentralized computer networktechnologies that, for example, maintain a secure and decentralizedrecord of transactions and/or otherwise protect the security of digitalinformation can likewise be employed. In various examples, a blockchaincan operate to collect information together in groups, such as blocks,that hold sets of information. These blocks have certain storagecapacities and, when filled, are closed and linked to the previouslyfilled blocks, forming a chain of data. New information that followsthat freshly added block is compiled into newly formed blocks that, oncefilled, can also be added to the chain.

As used herein the term “tool” corresponds to a utility, applicationand/or other software routine that performs one or more specificfunctions in conjunction with a computer.

It is noted that terminologies as may be used herein such as bit stream,stream, signal sequence, etc. (or their equivalents) have been usedinterchangeably to describe digital information whose contentcorresponds to any of a number of desired types (e.g., data, video,speech, text, graphics, audio, etc. any of which may generally bereferred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. For some industries, anindustry-accepted tolerance is less than one percent and, for otherindustries, the industry-accepted tolerance is 10 percent or more. Otherexamples of industry-accepted tolerance range from less than one percentto fifty percent. Industry-accepted tolerances correspond to, but arenot limited to, component values, integrated circuit process variations,temperature variations, rise and fall times, thermal noise, dimensions,signaling errors, dropped packets, temperatures, pressures, materialcompositions, and/or performance metrics. Within an industry, tolerancevariances of accepted tolerances may be more or less than a percentagelevel (e.g., dimension tolerance of less than +/−1%). Some relativitybetween items may range from a difference of less than a percentagelevel to a few percent. Other relativity between items may range from adifference of a few percent to magnitude of differences.

As may also be used herein, the term(s) “configured to”, “operablycoupled to”, “coupled to”, and/or “coupling” includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for an example of indirectcoupling, the intervening item does not modify the information of asignal but may adjust its current level, voltage level, and/or powerlevel. As may further be used herein, inferred coupling (i.e., where oneelement is coupled to another element by inference) includes direct andindirect coupling between two items in the same manner as “coupled to”.

As may even further be used herein, the term “configured to”, “operableto”, “coupled to”, or “operably coupled to” indicates that an itemincludes one or more of power connections, input(s), output(s), etc., toperform, when activated, one or more its corresponding functions and mayfurther include inferred coupling to one or more other items. As maystill further be used herein, the term “associated with”, includesdirect and/or indirect coupling of separate items and/or one item beingembedded within another item.

As may be used herein, the term “compares favorably”, indicates that acomparison between two or more items, signals, etc., indicates anadvantageous relationship that would be evident to one skilled in theart in light of the present disclosure, and based, for example, on thenature of the signals/items that are being compared. As may be usedherein, the term “compares unfavorably”, indicates that a comparisonbetween two or more items, signals, etc., fails to provide such anadvantageous relationship and/or that provides a disadvantageousrelationship. Such an item/signal can correspond to one or more numericvalues, one or more measurements, one or more counts and/or proportions,one or more types of data, and/or other information with attributes thatcan be compared to a threshold, to each other and/or to attributes ofother information to determine whether a favorable or unfavorablecomparison exists. Examples of such a advantageous relationship caninclude: one item/signal being greater than (or greater than or equalto) a threshold value, one item/signal being less than (or less than orequal to) a threshold value, one item/signal being greater than (orgreater than or equal to) another item/signal, one item/signal beingless than (or less than or equal to) another item/signal, oneitem/signal matching another item/signal, one item/signal substantiallymatching another item/signal within a predefined or industry acceptedtolerance such as 1%, 5%, 10% or some other margin, etc. Furthermore,one skilled in the art will recognize that such a comparison between twoitems/signals can be performed in different ways. For example, when theadvantageous relationship is that signal 1 has a greater magnitude thansignal 2, a favorable comparison may be achieved when the magnitude ofsignal 1 is greater than that of signal 2 or when the magnitude ofsignal 2 is less than that of signal 1. Similarly, one skilled in theart will recognize that the comparison of the inverse or opposite ofitems/signals and/or other forms of mathematical or logical equivalencecan likewise be used in an equivalent fashion. For example, thecomparison to determine if a signal X>5 is equivalent to determining if−X<−5, and the comparison to determine if signal A matches signal B canlikewise be performed by determining −A matches −B or not(A) matchesnot(B). As may be discussed herein, the determination that a particularrelationship is present (either favorable or unfavorable) can beutilized to automatically trigger a particular action. Unless expresslystated to the contrary, the absence of that particular condition may beassumed to imply that the particular action will not automatically betriggered. In other examples, the determination that a particularrelationship is present (either favorable or unfavorable) can beutilized as a basis or consideration to determine whether to perform oneor more actions. Note that such a basis or consideration can beconsidered alone or in combination with one or more other bases orconsiderations to determine whether to perform the one or more actions.In one example where multiple bases or considerations are used todetermine whether to perform one or more actions, the respective basesor considerations are given equal weight in such determination. Inanother example where multiple bases or considerations are used todetermine whether to perform one or more actions, the respective basesor considerations are given unequal weight in such determination.

As may be used herein, one or more claims may include, in a specificform of this generic form, the phrase “at least one of a, b, and c” orof this generic form “at least one of a, b, or c”, with more or lesselements than “a”, “b”, and “c”. In either phrasing, the phrases are tobe interpreted identically. In particular, “at least one of a, b, and c”is equivalent to “at least one of a, b, or c” and shall mean a, b,and/or c. As an example, it means: “a” only, “b” only, “c” only, “a” and“b”, “a” and “c”, “b” and “c”, and/or “a”, “b”, and “c”.

As may also be used herein, the terms “processing module”, “processingcircuit”, “processor”, “processing circuitry”, and/or “processing unit”may be a single processing device or a plurality of processing devices.Such a processing device may be a microprocessor, micro-controller,digital signal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module,module, processing circuit, processing circuitry, and/or processing unitmay be, or further include, memory and/or an integrated memory element,which may be a single memory device, a plurality of memory devices,and/or embedded circuitry of another processing module, module,processing circuit, processing circuitry, and/or processing unit. Such amemory device may be a read-only memory, random access memory, volatilememory, non-volatile memory, static memory, dynamic memory, flashmemory, cache memory, and/or any device that stores digital information.Note that if the processing module, module, processing circuit,processing circuitry, and/or processing unit includes more than oneprocessing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that if the processing module, module, processing circuit,processing circuitry and/or processing unit implements one or more ofits functions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element may store, and the processing module, module,processing circuit, processing circuitry and/or processing unitexecutes, hard coded and/or operational instructions corresponding to atleast some of the steps and/or functions illustrated in one or more ofthe FIGURES. Such a memory device or memory element can be included inan article of manufacture.

One or more examples have been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claims. Further, the boundariesof these functional building blocks have been arbitrarily defined forconvenience of description. Alternate boundaries could be defined aslong as the certain significant functions are appropriately performed.Similarly, flow diagram blocks may also have been arbitrarily definedherein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence couldhave been defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claims. One of average skill in the art will alsorecognize that the functional building blocks, and other illustrativeblocks, modules and components herein, can be implemented as illustratedor by discrete components, application specific integrated circuits,processors executing appropriate software and the like or anycombination thereof.

In addition, a flow diagram may include a “start” and/or “continue”indication. The “start” and “continue” indications reflect that thesteps presented can optionally be incorporated in or otherwise used inconjunction with one or more other routines. In addition, a flow diagrammay include an “end” and/or “continue” indication. The “end” and/or“continue” indications reflect that the steps presented can end asdescribed and shown or optionally be incorporated in or otherwise usedin conjunction with one or more other routines. In this context, “start”indicates the beginning of the first step presented and may be precededby other activities not specifically shown. Further, the “continue”indication reflects that the steps presented may be performed multipletimes and/or may be succeeded by other activities not specificallyshown. Further, while a flow diagram indicates a particular ordering ofsteps, other orderings are likewise possible provided that theprinciples of causality are maintained.

The one or more examples are used herein to illustrate one or moreaspects, one or more features, one or more concepts, and/or one or moreexamples. A physical example of an apparatus, an article of manufacture,a machine, and/or of a process may include one or more of the aspects,features, concepts, examples, etc. described with reference to one ormore of the examples discussed herein. Further, from figure to figure,the examples may incorporate the same or similarly named functions,steps, modules, etc. that may use the same or different referencenumbers and, as such, the functions, steps, modules, etc. may be thesame or similar functions, steps, modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of theexamples. A module implements one or more functions via a device such asa processor or other processing device or other hardware that mayinclude or operate in association with a memory that stores operationalinstructions. A module may operate independently and/or in conjunctionwith software and/or firmware. As also used herein, a module may containone or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes oneor more memory elements. A memory element may be a separate memorydevice, multiple memory devices, or a set of memory locations within amemory device. Such a memory device may be a read-only memory, randomaccess memory, volatile memory, non-volatile memory, static memory,dynamic memory, flash memory, cache memory, a quantum register or otherquantum memory and/or any other device that stores data in anon-transitory manner. Furthermore, the memory device may be in a formof a solid-state memory, a hard drive memory or other disk storage,cloud memory, thumb drive, server memory, computing device memory,and/or other non-transitory medium for storing data. The storage of dataincludes temporary storage (i.e., data is lost when power is removedfrom the memory element) and/or persistent storage (i.e., data isretained when power is removed from the memory element). As used herein,a transitory medium shall mean one or more of: (a) a wired or wirelessmedium for the transportation of data as a signal from one computingdevice to another computing device for temporary storage or persistentstorage; (b) a wired or wireless medium for the transportation of dataas a signal within a computing device from one element of the computingdevice to another element of the computing device for temporary storageor persistent storage; (c) a wired or wireless medium for thetransportation of data as a signal from one computing device to anothercomputing device for processing the data by the other computing device;and (d) a wired or wireless medium for the transportation of data as asignal within a computing device from one element of the computingdevice to another element of the computing device for processing thedata by the other element of the computing device. As may be usedherein, a non-transitory computer readable memory is substantiallyequivalent to a computer readable memory. A non-transitory computerreadable memory can also be referred to as a non-transitory computerreadable storage medium.

One or more functions associated with the methods and/or processesdescribed herein can be implemented via a processing module thatoperates via the non-human “artificial” intelligence (AI) of a machine.Examples of such AI include machines that operate via anomaly detectiontechniques, decision trees, association rules, expert systems and otherknowledge-based systems, computer vision models, artificial neuralnetworks, convolutional neural networks, support vector machines (SVMs),Bayesian networks, genetic algorithms, feature learning, sparsedictionary learning, preference learning, deep learning and othermachine learning techniques that are trained using training data viaunsupervised, semi-supervised, supervised and/or reinforcement learning,and/or other AI. The human mind is not equipped to perform such AItechniques, not only due to the complexity of these techniques, but alsodue to the fact that artificial intelligence, by its verydefinition—requires “artificial” intelligence—i.e. machine/non-humanintelligence.

One or more functions associated with the methods and/or processesdescribed herein involve NFTs that are generated (“minted”) and securedvia blockchain or other decentralized computer network technology. Thedistributed nature of these technologies over different nodes, thecontemporaneous nature of geographically distinct calculations, coupledwith the extreme computational complexity of the required calculationsmeans that these decentralized computer network technologies cannotpractically be performed by the human mind.

One or more functions associated with the methods and/or processesdescribed herein can be implemented as a large-scale system that isoperable to receive, transmit and/or process data on a large-scale. Asused herein, a large-scale refers to a large number of data, such as oneor more kilobytes, megabytes, gigabytes, terabytes or more of data thatare received, transmitted and/or processed. Such receiving, transmittingand/or processing of data cannot practically be performed by the humanmind on a large-scale within a reasonable period of time, such as withina second, a millisecond, microsecond, a real-time basis or other highspeed required by the machines that generate the data, receive the data,convey the data, store the data and/or use the data.

One or more functions associated with the methods and/or processesdescribed herein can require data to be manipulated in different wayswithin overlapping time spans. The human mind is not equipped to performsuch different data manipulations independently, contemporaneously, inparallel, and/or on a coordinated basis within a reasonable period oftime, such as within a second, a millisecond, microsecond, a real-timebasis or other high speed required by the machines that generate thedata, receive the data, convey the data, store the data and/or use thedata.

One or more functions associated with the methods and/or processesdescribed herein can be implemented in a system that is operable toelectronically receive digital data via a wired or wirelesscommunication network and/or to electronically transmit digital data viaa wired or wireless communication network. Such receiving andtransmitting cannot practically be performed by the human mind becausethe human mind is not equipped to electronically transmit or receivedigital data, let alone to transmit and receive digital data via a wiredor wireless communication network.

One or more functions associated with the methods and/or processesdescribed herein can be implemented in a system that is operable toelectronically store digital data in a memory device. Such storagecannot practically be performed by the human mind because the human mindis not equipped to electronically store digital data.

One or more functions associated with the methods and/or processesdescribed herein may operate to cause an action by a processing moduledirectly in response to a triggering event—without any intervening humaninteraction between the triggering event and the action. Any suchactions may be identified as being performed “automatically”,“automatically based on” and/or “automatically in response to” such atriggering event. Furthermore, any such actions identified in such afashion specifically preclude the operation of human activity withrespect to these actions—even if the triggering event itself may becausally connected to a human activity of some kind.

While particular combinations of various functions and features of theone or more examples have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent disclosure is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

What is claimed is:
 1. A method for use with a client device thatincludes a processor and a memory, that utilizes a graphical userinterface to interact with a user and that implements a walletconfigured to store non-fungible tokens (NFTs), the method comprising:reading, via the client device, an optical code associated with a gametoken; sending, via the client device and in response to reading theoptical code, a request to download a game token NFT associated with thegame token from an NFT distribution platform; receiving from the NFTdistribution platform, via the client device, the game token NFTassociated with the game token; and storing the game token NFT in awallet associated with the user.
 2. The method of claim 1, furthercomprising: determining when the client device has downloaded game tokenNFTs associated with each game token of a series of game tokens.
 3. Themethod of claim 2, further comprising: facilitating a game utilizing theseries of game tokens, via the client device, when the client device hasdownloaded game token NFTs associated with each game token of the seriesof game tokens.
 4. The method of claim 2, further comprising:facilitating a redemption transaction utilizing the series of gametokens, via the client device, when the client device has downloadedgame token NFTs associated with each game token of the series of gametokens.
 5. The method of claim 4, wherein facilitating the redemptiontransaction includes: generating a transaction request to redeem aseries of game token NFTs, wherein the transaction request includes gametoken NFT identification data identifying the series of game token NFTs;and sending the transaction request to the NFT distribution platform. 6.The method of claim 5, wherein the NFT distribution platform determineswhen the game token NFTs are authenticated, generates credentials datato grant the transaction request when the game token NFTs areauthenticated and sends the credentials data to the client device. 7.The method of claim 6, wherein the game token NFT identification data isretrieved from the wallet associated with the user.
 8. The method ofclaim 7, wherein the NFT distribution platform further determined whenownership of the series of game token NFTs is validated and onlygenerates credentials data to grant the transaction request when theuser's ownership of the series of game token NFTs is validated.
 9. Themethod of claim 1, wherein the NFT distribution platform mints the gametoken NFT responsive to the request to download.
 10. The method of claim1, wherein the game token NFT is minted prior to the request todownload.
 11. A client device comprises: a network interface configuredto communicate via a network; at least one processor; a camera; a touchscreen that generates a graphical user interface to interact with auser; a non-transitory machine-readable storage medium that storesoperational instructions that, when executed by the processor, cause theat least one processor to perform operations that include: providing awallet associated with the user configured to store non-fungible tokens(NFTs); reading, via the camera, an optical code associated with a gametoken; sending, via the network interface and in response to reading theoptical code, a request to download a game token NFT associated with thegame token from an NFT distribution platform; receiving from the NFTdistribution platform, via the network interface, the game token NFTassociated with the game token; and storing the game token NFT in thewallet associated with the user.
 12. The client device of claim 11,further comprising: determining when the client device has downloadedgame token NFTs associated with each game token of a series of gametokens.
 13. The client device of claim 12, further comprising:facilitating a game utilizing the series of game tokens, via the clientdevice, when the client device has downloaded game token NFTs associatedwith each game token of the series of game tokens.
 14. The client deviceof claim 12, further comprising: facilitating a redemption transactionutilizing the series of game tokens, via the client device, when theclient device has downloaded game token NFTs associated with each gametoken of the series of game tokens.
 15. The client device of claim 14,wherein facilitating the redemption transaction includes: generating atransaction request to redeem a series of game token NFTs, wherein thetransaction request includes game token NFT identification dataidentifying the series of game token NFTs; and sending the transactionrequest to the NFT distribution platform.
 16. The client device of claim15, wherein the NFT distribution platform determines when the game tokenNFTs are authenticated, generates credentials data to grant thetransaction request when the game token NFTs are authenticated and sendsthe credentials data to the client device.
 17. The client device ofclaim 16, wherein the game token NFT identification data is retrievedfrom the wallet associated with the user.
 18. The client device of claim17, wherein the NFT distribution platform further determined whenownership of the series of game token NFTs is validated and onlygenerates credentials data to grant the transaction request when theuser's ownership of the series of game token NFTs is validated.
 19. Theclient device of claim 11, wherein the NFT distribution platform mintsthe game token NFT responsive to the request to download.
 20. The clientdevice of claim 11, wherein the game token NFT is minted prior to therequest to download.